dc-hsdpa(ran16.0 draft a)

WCDMA RAN

DC-HSDPA Feature ParameterDescription

Issue Draft A

Date 2014-01-20

HUAWEI TECHNOLOGIES CO., LTD.

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

No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof 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 a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue Draft A (2014-01-20) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

Contents

1 About This Chapter.......................................................................................................................11.1 Scope..............................................................................................................................................................................11.2 Intended Audience..........................................................................................................................................................11.3 Change History...............................................................................................................................................................1

2 Overview.........................................................................................................................................5

3 Basic Principle................................................................................................................................63.1 Overview........................................................................................................................................................................63.2 DC-HSDPA Cells...........................................................................................................................................................73.2.1 Primary and Secondary Cells......................................................................................................................................73.2.2 Multi-Carrier Cell Groups...........................................................................................................................................93.3 DC-HSDPA+MIMO Cells.............................................................................................................................................93.4 Channel Mapping.........................................................................................................................................................103.4.1 Overview...................................................................................................................................................................103.4.2 HS-SCCH..................................................................................................................................................................113.4.3 HS-DPCCH...............................................................................................................................................................113.5 UE Categories...............................................................................................................................................................123.6 NodeB MAC-ehs..........................................................................................................................................................153.7 Impact on Interfaces.....................................................................................................................................................173.7.1 Overview...................................................................................................................................................................173.7.2 Impact on Iub.............................................................................................................................................................173.7.3 Impact on Uu.............................................................................................................................................................18

4 Technical Description.................................................................................................................194.1 Overview......................................................................................................................................................................194.2 Radio Bearers...............................................................................................................................................................194.3 State Transition.............................................................................................................................................................214.4 Mobility Management..................................................................................................................................................214.4.1 Overview...................................................................................................................................................................214.4.2 Measurement Control................................................................................................................................................214.4.3 Intra-Frequency Handover.........................................................................................................................................224.4.4 Inter-Frequency Handover.........................................................................................................................................224.4.5 Handover from a DC-HSDPA Cell to a Non-DC-HSDPA Cell...............................................................................23

WCDMA RANDC-HSDPA Feature Parameter Description Contents


ii

4.4.6 Handover from a Non-DC-HSDPA Cell to a DC-HSDPA Cell...............................................................................234.4.7 Inter-RAT Handover..................................................................................................................................................244.4.8 Handover Between RNCs..........................................................................................................................................244.5 Load Control.................................................................................................................................................................244.5.1 RAB DRD..................................................................................................................................................................244.5.2 Call Admission Control.............................................................................................................................................284.5.3 Queuing and Preemption...........................................................................................................................................294.5.4 Load Reshuffling and Overload Control...................................................................................................................294.6 Scheduling....................................................................................................................................................................30

5 Related Features ..........................................................................................................................325.1 WRFD-010696 DC-HSDPA........................................................................................................................................325.2 WRFD-010699 DC-HSDPA+MIMO...........................................................................................................................33

6 Network Impact ..........................................................................................................................356.1 WRFD-010696 DC-HSDPA........................................................................................................................................356.2 WRFD-010699 DC-HSDPA+MIMO...........................................................................................................................36

7 Engineering Guidelines.............................................................................................................377.1 WRFD-010696 DC-HSDPA .......................................................................................................................................377.1.1 When to Use DC-HSDPA.........................................................................................................................................377.1.2 Required Information................................................................................................................................................377.1.3 Planning.....................................................................................................................................................................387.1.4 Deployment...............................................................................................................................................................397.1.4.1 Requirements..........................................................................................................................................................397.1.4.2 Data Preparation.....................................................................................................................................................407.1.4.3 Precautions..............................................................................................................................................................417.1.4.4 Activation...............................................................................................................................................................417.1.4.4.1 Using MML Commands......................................................................................................................................427.1.4.4.2 MML Command Examples.................................................................................................................................437.1.4.4.3 Using the CME....................................................................................................................................................447.1.4.5 Activation Observation...........................................................................................................................................467.1.4.6 Deactivation............................................................................................................................................................487.1.4.6.1 Using MML Commands......................................................................................................................................487.1.4.6.2 MML Command Examples.................................................................................................................................487.1.4.6.3 Using the CME....................................................................................................................................................487.1.5 Performance Monitoring............................................................................................................................................497.1.5.1 Monitoring Counters...............................................................................................................................................497.1.5.2 Monitoring KPIs.....................................................................................................................................................507.1.6 Parameter Optimization.............................................................................................................................................517.1.7 Troubleshooting.........................................................................................................................................................517.2 WRFD-010699 DC-HSDPA+MIMO ..........................................................................................................................517.2.1 When to Use DC-HSDPA+MIMO............................................................................................................................51



iii

7.2.2 Required Information................................................................................................................................................527.2.3 Planning ....................................................................................................................................................................537.2.3.1 RF Planning............................................................................................................................................................537.2.3.2 Network Planning...................................................................................................................................................537.2.4 Deployment ..............................................................................................................................................................537.2.4.1 Requirements..........................................................................................................................................................537.2.4.2 Data Preparation.....................................................................................................................................................547.2.4.3 Precautions..............................................................................................................................................................547.2.4.4 Activation ..............................................................................................................................................................547.2.4.4.1 Using MML Commands......................................................................................................................................547.2.4.4.2 MML Command Examples.................................................................................................................................557.2.4.5 Activation Observation...........................................................................................................................................567.2.4.6 Deactivation ...........................................................................................................................................................567.2.4.6.1 Using MML Commands......................................................................................................................................577.2.4.6.2 MML Command Examples.................................................................................................................................577.2.5 Performance Monitoring............................................................................................................................................577.2.6 Parameter Optimization.............................................................................................................................................587.2.7 Troubleshooting.........................................................................................................................................................58

8 Parameters.....................................................................................................................................59

9 Counters......................................................................................................................................212

10 Glossary.....................................................................................................................................225

11 Reference Documents.............................................................................................................226



iv

1 About This Chapter

1.1 ScopeThis document describes DC-HSDPA, including its basic principles, related features, networkimpact, and engineering guidelines.

DC-HSDPA involves the following features:

l WRFD-010696 DC-HSDPA

l WRFD-010699 DC-HSDPA+MIMO

1.2 Intended AudienceThis document is intended for personnel who:

l Need to understand the features described herein

l Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions. There aretwo types of changes, which are defined as follows:

l Feature change

Changes in features of a specific product version

l Editorial change

Changes in wording or addition of information that was not described in the earlier version

Draft A (2014-01-20)

Compared with Issue 03 (2013-12-30) of RAN15.0, Draft A (2014-01-20) of RAN16.0 includesthe following changes.

WCDMA RANDC-HSDPA Feature Parameter Description 1 About This Chapter


1

Change Type Change Description Parameter Change

Feature change l Renamed theVS.CellReserve.Coun-ter4 counter"VS.DCHSDPA.DataTtiNum.User."

l Added the impacts of theWRFD-160103 TerminalBlack List feature on DC-HSDPA. For details, see5 Related Features .

None

Editorial change Modified the featureactivation. That is, for the3900 series base stations,BTS3902E, and BTS3803E,you are advised to run theDEA UCELL command todeactivate the MIMO Primecells to be added to a DC-HSDPA or DC-HSDPA+MIMO cell group beforeactivating DC-HSDPA orDC-HSDPA+MIMO.

None

03 (2013-12-30)Compared with Issue 02 (2013-06-30) of RAN15.0, Issue 03 (2013-12-30) of RAN15.0 includesthe following changes.


Feature change None None

Editorial change Added the WRFD-010699DC-HSDPA+MIMO feature.For details, see 3.3 DC-HSDPA+MIMO Cells, 5Related Features , 6Network Impact , and 7Engineering Guidelines.

None

02 (2013-06-30)This issue includes the following changes.



2

ChangeType

Change Description ParameterChange

Featurechange

None None

Editorialchange

Optimized section 7.1.5.1 Monitoring Counters. None

01 (2013-04-28)This issue includes the following changes.

Change Type Change Description ParameterChange

Feature change None None

Editorial change Added the restrictions for DC-HSDPA load-basedinter-frequency handover. For details, see 4.5.4Load Reshuffling and Overload Control

None

Draft A (2013-01-30)Compared with Issue 02 (2012-07-20) of RAN14.0, Draft A (2013-01-30) of RAN15.0 includesthe following changes.


Feature change Added the use of non-adjacentfrequencies at the same frequencyband for DC-HSDPA. For details,see the following sections:l 3.1 Overviewl 3.5 UE Categories

None

Changed the commands used forconfiguring DC-HSDPA groupsfrom ADD DLDUALCELLGRPto ADD NODEBMULTI-CELLGRP and ADDNODEBMULTICELLGRPI-TEM. For details, see section 3.2.2Multi-Carrier Cell Groups.

None



3


Editorial change Improved the description in thefollowing sections:l 4.2 Radio Bearersl 4.3 State Transitionl 4.4 Mobility Managementl 4.5 Load Controll 5 Related Featuresl 6 Network Impactl 7 Engineering Guidelines

None

Moved the description of theTraffic-Based Activation andDeactivation of the SupplementaryCarrier In Multi-carrier feature toTraffic-Based Activation andDeactivation of the SupplementaryCarrier In Multi-carrier FeatureParameter Description.

None



4

2 Overview

Similar to Long Term Evolution (LTE), High Speed Packet Access (HSPA) is also influencedby multi-carrier aggregation. Multi-carrier aggregation enables HSPA to obtain higherbandwidth, better performance, and greater user throughput. The user throughput of multi-carrierHSPA can be twice or more times that of single-carrier HSPA.

In versions earlier than 3GPP Release 8, a UE uses only a single carrier for HSDPA transmission.The use of a single carrier for HSDPA transmission is referred to as SC-HSDPA in this document.

3GPP Release 8 introduces DC-HSDPA. DC-HSDPA uses two adjacent carriers for HSDPAtransmission of a UE, doubling UE downlink throughput. 3GPP Release 10 (TS 25.331)enhances DC-HSDPA by allowing two non-adjacent carriers for HSDPA transmission of a UE.

Table 2-1describes the requirements of DC-HSDPA for network elements (NEs).

Table 2-1 Requirements for NEs

Item Requirement

CN None

RNC The RNC must support the Downlink Enhanced L2 feature.The RNC must provide the radio bearer scheme for DC-HSDPA.

NodeB The NodeB must support MAC-ehs. A single MAC-ehs entity supports HS-DSCH transmission in multiple cells served by the same NodeB (FDDonly).

UE In 3GPP Release 8, HS-DSCH UE categories 21, 22, 23, 24, 25, 26, 27, 28,29, 30, 31, and 32 are introduced to support DC-HSDPA. In 3GPP Release9 or later, more HS-DSCH UE categories are introduced to support DC-HSDPA.

WCDMA RANDC-HSDPA Feature Parameter Description 2 Overview


5

3 Basic Principle

3.1 OverviewDC-HSDPA allows a UE to set up HSDPA connections with two inter-frequency co-coveragecells. In the downlink, the UE can simultaneously receive data over HS-DSCHs in the two cells.In the uplink, the UE using the DCH or SC-HSUPA transmits data only in the primary cell. Thisdocument describes only the DC-HSDPA UEs whose uplink connections are established on theDCH or SC-HSUPA. For details about the DC-HSDPA UEs whose uplink connections areestablished on the DC-HSUPA, see DC-HSUPA Feature Parameter Description.

Figure 3-1 shows an example of uplink and downlink data transmission for a DC-HSDPA UE.

Figure 3-1 Example of uplink and downlink data transmission for a DC-HSDPA UE

The two cells (primary cell and secondary cell) of DC-HSDPA must meet the followingrestrictions:

WCDMA RANDC-HSDPA Feature Parameter Description 3 Basic Principle


6

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

l The two cells are in the same downlink resource group of a NodeB.l The two cells operate on frequencies that belong to the same frequency band.

The frequencies can be either adjacent or non-adjacent. Two frequencies are considered adjacentif the spacing between their center frequencies is less than or equal to 5 MHz. Two frequenciesare considered non-adjacent if the spacing between their center frequencies is an integer multipleof 5 MHz. Figure 3-2 shows adjacent and non-adjacent frequencies.

Figure 3-2 Adjacent and non-adjacent frequencies

l The two cells have the same time offset (specified by the Tcell parameter).l The two cells support HSDPA and the Downlink Enhanced L2 feature.l The dual cell transmission applies only to HSDPA physical channels.

DC-HSDPA improves the throughput and delay of users in the whole cell even at the cell edge.Theoretically, DC-HSDPA with 64QAM provides a downlink peak data rate of 42 Mbit/s, whichis twice the peak rate provided by 64QAM.

In multioperator core network (MOCN) or RAN sharing scenarios, the two DC-HSDPA cellscan belong to different operators.

3.2 DC-HSDPA Cells

3.2.1 Primary and Secondary CellsA DC-HSDPA group consists of two cells: the primary cell and secondary cell.

From the UE perspective:



7

l Primary cell (also called anchor cell) carries all the types of channels for a UE. Each UEhas only one primary cell.

l Secondary cell (also called supplementary cell) carries only three types of downlink (DL)channels for a UE. Each UE has only one secondary cell.The three types of DL channels are as follows:– HS-SCCH– HS-PDSCH– P-CPICH

The UARFCNDownlink and UARFCNUplink parameters in the MOD UCELLSETUPcommand specify the downlink and uplink operating frequency of a cell, respectively.

Figure 3-3 shows the physical channels available for a DC-HSDPA UE.

Figure 3-3 Cell configuration from the UE perspective

When the cells in a DC-HSDPA group are configured with the same types of common channelsas shown in Figure 3-4, either cell can serve as a primary cell. In addition, both cells can provideservices for SC-HSDPA and R99 users. The RNC selects a primary cell for a DC-HSDPA UEbased on the cell load and radio bearer policy. For details, see section 4.5.1 RAB DRD.

If a DC-HSDPA cell also has multiple-input multiple-output (MIMO) enabled, the DC-HSDPAcell can be configured with an S-CPICH.

Figure 3-4 Primary and secondary cells configured with the same types of common channels



8

If the primary cell is configured with all the common channels shown in Figure 3-4, and if thesecondary cell is configured with the HS-PDSCH, HS-SCCH, and P-CPICH, the secondary cellcannot provide services for SC-HSDPA and R99 users. Currently, Huawei DC-HSDPA doesnot support such configurations.

3.2.2 Multi-Carrier Cell GroupsDC-HSDPA requires two inter-frequency co-coverage cells. These two cells are configured asa multi-carrier cell group on the NodeB side as follows:

1. Run the NodeB MML command ADD NODEBMULTICELLGRP to add a multi-carriercell group.

2. Run the NodeB MML command ADD NODEBMULTICELLGRPITEM to add the twoDC-HSDPA cells to the multi-carrier cell group.

The NodeB reports information about cells in each multi-carrier cell group to the RNC over theIub interface. The RNC selects a primary cell and a secondary cell for a DC-HSDPA UE basedon the received cell information. For details, see section 4.5.1 RAB DRD.

NOTE

When the cells in a DC-HSDPA cell group operate on non-adjacent frequencies, UEs must support non-adjacent frequencies in the same frequency band.

The Tcell parameter must be set to the same value for the cells in a DC-HSDPA cell group.

After an upgrade to RAN15.0, DC-HSDPA cell groups are configured and managed through theADD/RMV/LST NODEBMULTICELLGRP commands, and existing DC-HSDPA cellgroups automatically change to multi-carrier cell groups. In RAN13.0, DC-HSDPA cell groupsare configured and managed through the ADD/RMV/LST DUALCELLGRP commands. InRAN14.0, DC-HSDPA cell groups are configured and managed through the ADD/RMV/LSTDLDUALCELLGRP commands.

3.3 DC-HSDPA+MIMO Cells

Configuration Modes of DC-HSDPA+MIMO Cell Groups

Figure 3-5 shows the configuration modes of the two cells in a DC-HSDPA+MIMO cell group.

Figure 3-5 Configuration modes of the two cells in a DC-HSDPA+MIMO cell group

The configuration modes allowed by DC-HSDPA cell groups are listed in Table 3-1.



9

Table 3-1 Configuration modes of the two cells in a DC-HSDPA cell group

Configuration Mode Cell 1 Cell 2 Peak Rate

DC+2xMIMO+2x64QAM MIMO+64QAM MIMO+64QAM 14 x 2 x 1.5 + 14 x 2x 1.5 = 84 Mbit/s

DC+1xMIMO+2x64QAM MIMO+64QAM 64QAM 14 x 2 x 1.5 + 14 x 1x 1.5 = 63 Mbit/s

DC+1xMIMO+1x64QAM MIMO+64QAM HSDPA 14 x 2 x 1.5 + 14 x 1x 1 = 56 Mbit/s

MIMO 64QAM 14 x 2 x 1 + 14 x 1 x1.5 = 49 Mbit/s

DC+2xMIMO MIMO MIMO 14 x 2 + 14 x 2 = 56Mbit/s

DC+1xMIMO MIMO HSDPA 14 x 2 + 14 = 42Mbit/s

3.4 Channel Mapping

3.4.1 Overview

Figure 3-6 Channel mapping of DC-HSDPA

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

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



10

3.4.2 HS-SCCHIn versions earlier than 3GPP Release 8, a UE can monitor a maximum of four HS-SCCHs atthe same time, according to 3GPP TS 25.214. In a DC-HSDPA cell group, the HS-SCCHs onthe primary cell are independent of those on the secondary cell. A UE can monitor a maximumof six HS-SCCHs at the same time. In each cell, the UE can monitor a maximum of three HS-SCCHs at the same time.

There are three types of HS-SCCHs: type 1 for cells enabled with neither MIMO nor HS-SCCHLess Operation, type 2 for cells enabled with HS-SCCH Less Operation, and type 3 for cellsenabled with MIMO. DC-HSDPA uses only HS-SCCH type 1. DC-HSDPA with HS-SCCHLess Operation uses HS-SCCH type 2.

HS-SCCH Less Operation applies only to the primary cell. In addition, HS-SCCH LessOperation is mutually exclusive with MIMO.

For details, see section 6A.1.1 UE procedure for receiving HS-DSCH and HS-SCCH in theCELL_DCH state in 3GPP TS 25.214 V9.8.0.

3.4.3 HS-DPCCHThe DC-HSDPA UE reports the CQI and HARQ ACK/NACK information about the two cellson the HS-DPCCH in the primary cell. The HS-DPCCH uses a new frame format that enablesit to carry CQI and HARQ ACK/NACK information about the two cells in a transmission timeinterval (TTI).

The coding and multiplexing schemes for the HS-DPCCH are enhanced to support DC-HSDPA+MIMO. The HS-DPCCH has four coding and multiplexing schemes, which are applicable tothe following scenarios:

l HSDPA: The UE is not configured in MIMO mode, and the secondary cell is not configuredor activated.

l MIMO: The UE is configured in MIMO mode or DC-HSDPA+MIMO mode, and thesecondary cell is not configured or activated.

l DC-HSDPA: The UE is not configured in MIMO mode, and the secondary cell is activated.l DC-HSDPA+MIMO: The UE is configured in MIMO mode, and the secondary cell is

activated.

Figure 3-7 shows the coding and multiplexing scheme for the HS-DPCCH when DC-HSDPA+MIMO is enabled.

Figure 3-7 Coding and multiplexing scheme for the HS-DPCCH when DC-HSDPA+MIMO isenabled

The ACK and NACK messages are coded and multiplexed onto the same timeslot of a subframe.The Precoding Control Indication (PCI) and Channel Quality Indicator (CQI) are multiplexedonto different subframes by using Time Division Multiplexing (TDM).



11

If a UE is configured in MIMO mode in one cell of a DC-HSDPA cell group, the coding schemesare as follows:

l The coding scheme for HARQ-ACK is the same as that used by a UE configured in MIMOmode in both cells of a DC-HSDPA cell group.

l If the cell is configured with MIMO, the coding and multiplexing scheme for the PCI andCQI is the same as that for HS-DPCCH in MIMO scenarios.

l If the cell is not configured with MIMO, the coding and multiplexing scheme for the PCIand CQI is the same as that for HS-DPCCH in HSDPA scenarios.

For details, see section 4.7 Coding for HS-DPCCH in 3GPP TS 25.212 V10.4.0.

3.5 UE CategoriesUEs must belong to HS-DSCH category 21 or higher to support DC-HSDPA and must belongto HS-DSCH category 25, 26, 27, 28, 30, or 32 to support DC-HSDPA+MIMO, as listed inTable 3-2. For details about HS-DSCH UE categories, see section 5 Possible UE radio accesscapability parameter settings in 3GPP TS 25.306 V10.4.0.

Table 3-2 FDD HS-DSCH physical layer categories 21 to 32

HS-DSCHCategory

MaximumNumber of HS-DSCHCodesReceived

MinimumInter-TTIInterval

MaximumNumber ofBits ofan HS-DSCHTransportBlockReceivedWithin anHS-DSCHTTI

TotalNumber ofSoftChannel Bits

SupportedModulationWithoutMIMOOperation orDualCellOperation

SupportedModulationSimultaneous withMIMOOperationandWithoutDualCellOperation

SupportedModulationwithDualCellOperation

SupportedModulationwithMIMO andDualCellOperation

Category 21

15 1 23370 345600 - - QPSK,16QAM

-

Category 22

15 1 27952 345600

Category 23

15 1 35280 518400 QPSK,16QAM,64QAM

Category 24

15 1 42192 518400



12

HS-DSCHCategory









Category 25

15 1 23370 691200 - - - QPSK,16QAM

Category 26

15 1 27952 691200

Category 27

15 1 35280 1036800

- - - QPSK,16QAM,64QAM

Category 28

15 1 42192 1036800

Category 29

15 1 42192 777600 - - QPSK,16QAM,64QAM

-

Category 30

15 1 42192 1555200

- - QPSK,16QAM,64QAM

QPSK,16QAM,64QAM

Category 31

15 1 42192 1036800


-



13

HS-DSCHCategory









Category 32

15 1 42192 2073600


QPSK,16QAM,64QAM

The scheduling algorithm of DC-HSDPA+MIMO needs to use the I, J, and K in the new CQItable to implement TFRC. Table 3-3 describes the mapping between HS-DSCH UE categoriesand CQIs. For details, see 6A.2.3 CQI tables in 3GPP TS 25.214.

Table 3-3 Mapping between HS-DSCH UE categories and CQIs

HS-DSCHCategory

MIMO NotConfigured

MIMO Configured and Single-StreamRestriction Not Configured

MIMO andSingle-StreamRestrictionConfigured

64QAM NotConfigured

64QAMConfigured

64QAM NotConfigured

64QAM Configured 64QAM NotConfigured

64QAMConfigured



14

In Caseof TypeB orSingleTransportBlockType ACQIReports

In Caseof DualTransportBlockType ACQIReports

In Caseof TypeB orSingleTransportBlockType ACQIReports

In Caseof DualTransportBlockType ACQIReports

25 C N/A C H N/A C N/A

26 D N/A D I N/A D N/A

27 C F C H F J C F

28 D G D I G K D G

30 and32

D G D I G K N/A

According to 3GPP Release 10, non-adjacent frequencies at the same frequency band can beused for HSDPA transmission of a UE. The "Non-contiguous multi-cell" IE in the "UE radioaccess capability extension" IE in an RRC CONNECTION SETUP COMPLETE messagespecifies whether a UE supports non-adjacent frequencies. A UE's capability to support non-adjacent frequencies is not related to its HS-DSCH category.

l When the "Aggregated cells" IE in the "Non-contiguous multi-cell" IE is nc-2c, the UEsupports two non-adjacent frequencies at the same frequency band.

l The "Gap size" IE in the "Non-contiguous multi-cell" IE specifies the spacing between thetwo non-adjacent frequencies supported by the UE. This IE can be set to fiveMHz, tenMHz,or anyGapSize. "fiveMHz" indicates that the UE supports a maximum of 5 MHz spacingbetween two non-adjacent frequencies. "tenMHz" indicates that the UE supports 5 and 10MHz spacing between two non-adjacent frequencies. "anyGapSize" indicates that the UEsupports any integer multiples of 5 MHz spacing between two non-adjacent frequencies.

l When a UE does not use DC-HSDPA after accessing a DC-HSDPA cell, the RNC performsfallback on the UE if the UE belongs to a certain HS-DSCH category. For details aboutHS-DSCH categories that support fallback in such a circumstance, see section 8.1.6Transmission of UE capability information in 3GPP TS 25.331 V10.10.0.

The peak rate of a DC-HSDPA UE can reach 42.192 Mbit/s (= 2 x TB_Size/TTI = 2 x 42192/2)at the MAC layer. The peak rate of a DC-HSDPA+MIMO UE can reach 84.384 Mbit/s (= 2 x2 x TB_Size/TTI = 2 X 2 X 42192/2) at the MAC layer. These peak rates require the supportfrom the CN.

3.6 NodeB MAC-ehsDC-HSDPA requires the NodeB to support MAC-ehs. A single MAC-ehs entity supports HS-DSCH transmission in more than one cell served by the same NodeB (FDD only). Queues of a



15

DC-HSDPA UE are common for the two cells. The scheduler in the NodeB arranges the datatransmission of queues on the two cells. DC-HSDPA transmissions can be regarded asindependent transmissions over two HS-DSCH channels. There will be a separate HARQ entityon each HS-DSCH channel, that is, one HARQ process per TTI for single carrier transmissionand two HARQ processes per TTI for dual carrier transmission.

MAC-ehs selects Transport Format and Resource Combination (TFRC) for the MAC-ehsProtocol Data Units (PDUs) of each cell independently based on the available resources of thecells and the CQI reported by the UE.

Figure 3-8 MAC-ehs architecture

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



16

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

3.7 Impact on Interfaces

3.7.1 OverviewTo support DC-HSDPA/DC-HSDPA+MIMO, new Information Elements (IEs) are added tosignaling messages.

UEs and NodeBs can report their capacity of DC-HSDPA/DC-HSDPA+MIMO to the RNCthrough the Iub and Uu interfaces.

l The RNC instructs cells to set up or reconfigure radio links with DC-HSDPA/DC-HSDPA+MIMO through the Iub interface.

l The RNC instructs UEs to set up or reconfigure radio bearers with DC-HSDPA/DC-HSDPA+MIMO through the Uu interface.

3.7.2 Impact on IubWhen a cell receives the AUDIT REQUEST message or when a new cell is set up or a cellcapability is changed, the NodeB reports the cell capability to the RNC in Audit Responsemessage or Resource State Indication message

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

l If the cell is a primary serving cell, all the possible secondary serving cells in the samesector must be listed 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 thesecondary serving cell is added to the Radio Link Setup procedure or Radio Link Additionprocedure.



17

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

3.7.3 Impact on UuIn the RRC CONNECTION REQUEST message, the Multi cell support IE is added to indicatethe UE capability of supporting multiple cells.

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

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

l RRC CONNECTION SETUPl ACTIVE SET UPDATEl CELL UPDATE CONFIRMl PHYSICAL CHANNEL RECONFIGURATIONl TRANSPORT CHANNEL RECONFIGURATIONl RADIO BEARER RECONFIGURATIONl RADIO BEARER RELEASEl RADIO BEARER SETUP



18

4 Technical Description

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

These functions are as follows:

l Radio Bearersl State transitionl Mobility managementl Load controll Scheduling

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

4.2 Radio BearersWhen the downlink transport channel HS-DSCH is selected for streaming or BE services orcombined service with streaming or BE, DC-HSDPA/DC-HSDPA+MIMO can be applied.When there is only a CS service, PS conversational service, IMS signaling, or SRB signaling,DC-HSDPA/DC-HSDPA+MIMO is not applied because of small traffic volume.

To enable DC-HSDPA to carry services, perform the following configurations:

l On the NodeB sideConfigure DC-HSDPA cells. For details about how to configure DC-HSDPA cells, seesection 3.2 DC-HSDPA Cells.

l On the RNC side

– Select CFG_HSDPA_DC_SWITCH in the RNC-level parameter CfgSwitch to enableDC-HSDPA to carry services. The CfgSwitch parameter is in the SETUCORRMALGOSWITCH command.

WCDMA RANDC-HSDPA Feature Parameter Description 4 Technical Description


19

– Select DC_HSDPA in the cell-level parameter HspaPlusSwitch to enable DC-HSDPAin the cell. The HspaPlusSwitch parameter is set in the ADDUCELLALGOSWITCH and MOD UCELLALGOSWITCH commands.

– Set MIMO64QAMorDcHSDPASwitch in the SET UFRC command to DC_HSDPAto select DC-HSDPA as the preferential HSPA+ technology for the cell.

When both the network and the UE support DC-HSDPA, the UE can use DC-HSDPA for datatransmission, regardless of the UE's subscribed rate. That is, the UE can use DC-HSDPA fordata transmission even if the UE's subscribed rate is less than 42 Mbit/s. For details, see RadioBearers Feature Parameter Description.

The Continuous Packet Connectivity (CPC) function can be enabled in the DC-HSDPA cellswith the following limitations:

l CPC DTX is applicable to primary cell only because there will be no uplink control channelfor the DC-HSDPA UE on secondary cell

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

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

DC-HSDPA and 64QAM can be used at the same time. 64QAM can be enabled in one orboth cells in a DC-HSDPA cell group. When both cells in a DC-HSDPA cell group have64QAM enabled, the peak downlink rate can reach 42 Mbit/s.

When a file is being downloaded, the TCP acknowledgement is sent in the uplink. Thehigher the rate of download is, the larger the bandwidth is required in the uplink. If thedownload rate reaches up to 42 Mbit/s, the uplink rate of TCP acknowledgement is muchhigher than 384 kbit/s, the highest supported by the DCH. HSUPA is required to providehigh bandwidth in the uplink to transmit TCP acknowledgement without delay. Thedownlink rate of 42 Mbit/s per user can be supported only when HSUPA is used.

Only UEs complying with 3GPP Release 9 and later support DC-HSDPA+MIMO. Table 4-1describes the implementation of DC-HSDPA+MIMO in Huawei products.

Table 4-1 Implementation of DC-HSDPA+MIMO in Huawei products

Version Implementation

Supports DC-HSDPA+MIMO

Number of CellsSupporting MIMO ina DC-HSDPA Group

SupportsSimultaneous Use ofDC-HSDPA andMIMO for UEs

RAN12.0 Yes 1 No

RAN13.0 Yes 2 Yes

RAN14.0 Yes 2 Yes

When the HS-DSCH is used for data transmission, the radio bearer policy of DC-HSDPA+MIMO is as follows:



20

l If a cell and UEs in this cell support DC-HSDPA+MIMO, services of these UEs use DC-HSDPA+MIMO.

l If a cell and UEs in this cell support only DC-HSDPA or MIMO, services of these UEs useonly DC-HSDPA or MIMO.

l If a cell and UEs in this cell support both DC-HSDPA and MIMO but do not support DC-HSDPA+MIMO, services of these UEs use the preferred HSPA+ technology for the cell.The preferred HSPA+ technology for a cell is specified by theMIMO64QAMorDCHSDPASwitch parameter in the SET UFRC command.

NOTE

For details about transport channel selection, see Radio Bearers Feature Parameter Description.

4.3 State TransitionDC-HSDPA UEs only support the CELL_DCH state. After DC-HSDPA UEs transition to otherstates, they cannot be carried on DC-HSDPA. DC-HSDPA UEs can perform state transition onlyin the primary cell.

When a UE supporting DC-HSDPA transitions from the CELL_FACH, CELL_PCH, orURA_PCH state to the CELL_DCH state, the RNC establishes a DC-HSDPA radio bearer (RB)for the UE. After the state transition is complete, the RNC performs RAB DRD to select anappropriate DC-HSDPA group for the UE. For details, see section 4.5.1 RAB DRD.

NOTE

DC-HSDPA RB refers to the HSDPA RB that has DC-HSDPA enabled.

The state transition trigger threshold for DC-HSDPA UEs is the same as that for SC-HSDPAUEs. For details, see State Transition Feature Parameter Description.

DC-HSDPA+MIMO applies the same principles as DC-HSDPA in state transition.

4.4 Mobility Management

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

This section describes only the mobility management of DC-HSDPA. For other informationabout handover, see Handover Feature Parameter Description.

4.4.2 Measurement ControlWhen DC-HSDPA is enabled, the RNC maintains the active set only in the primary cell.

Intra-frequency measurement control for DC-HSDPA UEs is the same as that for SC-HSDPAUEs.

DC-HSDPA UEs can perform inter-frequency measurements in the following modes:



21

l Compressed modeInter-frequency measurement control for DC-HSDPA UEs in compressed mode is the sameas that for SC-HSDPA UEs in compressed mode.

l Non-compressed modeDC-HSDPA UEs perform inter-frequency measurements in non-compressed mode whenall of the following conditions are met:– CMP_UU_ADJACENT_FREQ_CM_SWITCH in the CmpSwitch parameter for the

SET UCORRMALGOSWITCH command is selected.When CMP_UU_ADJACENT_FREQ_CM_SWITCH is selected, the UE canperform inter-frequency measurements in non-compressed mode on frequencies spacedless than or equal to 5 MHz from the operating frequency of the UE. For a DC-HSDPAnetwork, it is recommended that this switch be turned off, because the UE currentlycannot report whether it is allowed to use the non-compressed mode for frequencies ofneighboring cells within 5 MHz from the current frequency.

– The value of the following IE in the RRC CONNECTION SETUP COMPLETEmessage sent by the UE is TRUE: "UE radio access capability" IE > "Measurementcapability" IE > "Adjacent frequency measurements without compressed mode" IE.

– If UEs are performing DC-HSDPA services, the UE performs inter-frequencymeasurements only in the cells operating on the same frequency as the secondary celland the frequency is spaced less than or equal to 5 MHz from the operating frequencyof the current cell.

– If UEs are not performing DC-HSDPA services, the UE performs inter-frequencymeasurements in the cells that meet the following conditions:-The cells operate on the same frequency at the same frequency band as the current cell.-The cells operate on frequencies whose center frequencies are spaced less than or equalto 5 MHz away from the center frequency of the current cell.-All cells to be measured operate on the same frequency.

4.4.3 Intra-Frequency HandoverWhen receiving a measurement report from a DC-HSDPA UE indicating that the signal qualityof a DC-HSDPA cell is better than that of the serving cell (a DC-HSDPA cell), the RNC decideswhether to perform a DC-HSDPA handover to the target cell:

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

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

l If the admission to the target cell is not allowed, the RNC reconfigures the service on theDCH and performs a DCH handover:– If the DCH handover is allowed, the RNC performs the handover.– Otherwise, the RNC does not perform the handover.

4.4.4 Inter-Frequency HandoverDuring an inter-frequency handover, the DC-HSDPA UE needs to measure the signal quality ofthe primary cell and its neighboring cells. If the secondary cell is a neighboring cell of the primary



22

cell, the DC-HSDPA UE also needs to measure the signal quality of the secondary cell. Theinter-frequency handover process for DC-HSDPA UEs is the same as that for SC-HSDPA UEs.For details about inter-frequency handovers, see Handover Feature Parameter Description.

4.4.5 Handover from a DC-HSDPA Cell to a Non-DC-HSDPA CellUpon receiving a measurement report from a DC-HSDPA UE indicating that the signal qualityof an inter-frequency non-DC-HSDPA cell is better than that of the serving cell (a DC-HSDPAcell), the RNC initiates an RB reconfiguration procedure to make the service be carried on theDCH or HSDPA and meanwhile performs a handover.

Upon receiving a measurement report carrying the signal quality of intra-frequency non-DC-HSDPA cells, the RNC performs different operations in different scenarios. Details are asfollows:

l If an intra-frequency non-DC-HSDPA cell in the active set reports event 1D:

– The RNC initiates an RB reconfiguration procedure to make the service be carried onthe DCH or HSDPA and meanwhile initiates a serving cell change procedure whenCMP_UU_SERV_CELL_CHG_WITH_RB_MOD_SWITCH in the CmpSwitchparameter is selected.

– The RNC initiates an RB reconfiguration procedure to make the service be carried onthe DCH or HSDPA and then initiates a serving cell change procedure whenCMP_UU_SERV_CELL_CHG_WITH_RB_MOD_SWITCH in the CmpSwitchparameter is deselected.

l If an intra-frequency non-DC-HSDPA cell outside the active set reports event 1D:

– The RNC initiates an RB reconfiguration procedure to make the service be carried onthe DCH or HSDPA and then initiates an active set update procedure with serving cellchange when CMP_UU_SERV_CELL_CHG_WITH_ASU_SWITCH in theCmpSwitch parameter is selected.

– The RNC initiates an RB reconfiguration procedure to make the service be carried onthe DCH or HSDPA, initiates an active set update procedure, and then initiates a servingcell change procedure whenCMP_UU_SERV_CELL_CHG_WITH_ASU_SWITCH in the CmpSwitchparameter is deselected.

The CmpSwitch parameter is set using the SET UCORRMALGOSWITCH command.

4.4.6 Handover from a Non-DC-HSDPA Cell to a DC-HSDPA CellUpon receiving a measurement report indicating that the signal quality of a DC-HSDPA cell isbetter than that of the serving cell (a non-HSDPA cell), the RNC performs a handover afterwhich the HSPA+ technologies supported by both the source cell and the target cell are used inthe target cell. If such HSPA+ technologies are ranked lower than some HSPA+ technologiessupported by both the target cell and the UE, the ChannelRetryHoTimerLen timer is startedafter the handover. When the timer expires, the RNC tries to reconfigure the traffic radio bearer(TRB) and signaling radio bearer (SRB) to enable them to support the higher-ranked HSPA+technologies. If the reconfiguration fails, the RNC starts the retry timer(ChannelRetryTimerLen) for periodic retry attempts.

The HSPA+ technologies that can be retried are specified by the parameter RetryCapability inthe SET UFRC command.



23

The ChannelRetryHoTimerLen and ChannelRetryTimerLen parameters are set using the SETUCOIFTIMER command.

4.4.7 Inter-RAT HandoverThe inter-RAT handover process for DC-HSDPA UEs is the same as that for SC-HSDPA UEs.For details about inter-RAT handovers, see Handover Feature Parameter Description.

After a UE is handed over to a DC-HSDPA cell from a cell belonging to another RAT, the UEis carried on HSDPA. The RNC starts a retry timer as soon as the handover is complete. Whenthe timer expires, the RNC initiates an RB reconfiguration procedure to make the UE carried onDC-HSDPA or a higher HSPA+ technology. If the reconfiguration fails, the RNC starts the retrytimer for periodic DRD.

The ChannelRetryTimerLen parameter in the SET UCOIFTIMER command specifies theretry timer.

4.4.8 Handover Between RNCsThe current version does not support the handover between different RNCs for DC-HSDPAusers.

During the handover, if the target cell is from different RNC, the DC-HSDPA user falls back toSC-HSDPA and then the handover is performed.

Upon completion of the handover, if DC-HSDPA is included in HSPA technologies that can beretried by UEs (that is, DC-HSDPA under the RetryCapability parameter is turned on) and thehandover target cell supports DC-HSDPA, the RNC will attempt to switch the services on DC-HSDPA RABs.

4.5 Load Control

4.5.1 RAB DRDDuring a RAB setup or a state transition from CELL_FACH to CELL_DCH, the RNC performsDRDs to select a primary cell and a secondary cell for DC-HSDPA/DC-HSDPA+MIMO UEs.This section describes the DRD for DC-HSDPA/DC-HSDPA+MIMO UEs. For more detailsabout DRD, see Directed Retry Decision Feature Parameter Description.

DRD ProcedureFigure 4-1 outlines the DRD procedure.



24

Figure 4-1 DRD procedure



25

1. The RNC selects cells that meet the quality requirements of inter-frequency DRD ascandidate cells.

For details about the quality requirements of inter-frequency DRD, see section 4.2.1 "Inter-Frequency DRD" in Directed Retry Decision Feature Parameter Description.

2. The RNC performs the following operations to select a cell from candidate cells as theprimary cell.

When DRD for device type steering is enabled, the RNC selects the candidate cell with thehighest device type steering priority as the primary cell and proceeds to step 3. If multiplecandidate cells all have the highest device type steering priority or if DRD for device typesteering is disabled, proceed to step (b).

For details about how to select candidate cells based on device type steering, see section4.2.2 "Inter-Frequency DRD for Device Type Steering" in Directed Retry Decision FeatureParameter Description.

(b) When DRD for HSPA+ technological satisfaction is enabled, the RNC selects thecandidate cell with the highest HSPA+ technological satisfaction as the primary cell andproceeds to step 3. If multiple candidate cells all have the highest HSPA+ technologicalsatisfaction or if DRD for HSPA+ technological satisfaction is disabled, proceed to step(c).

For details about how to select candidate cells based on the HSPA+ technologicalsatisfaction, see section 4.2.3 "Inter-Frequency DRD for Technological Satisfaction" inDirected Retry Decision Feature Parameter Description.

(c) When DRD for service steering is enabled, the RNC selects the candidate cell with thehighest service priority as the primary cell and proceeds to step 3. If multiple candidatecells all have the highest service priority or if DRD for service steering is disabled, proceedto step (d).

For details about how to select candidate cells based on the service priority, see sectionService Priority-based Cell Selection.

(d) When DRD for UE location is enabled, the RNC selects a candidate cell as the primarycell based on DRD for UE location and proceeds to step 3. If multiple candidate cells meetthe requirements of DRD for UE location, proceed to step (e).

For details about how to select candidate cells based on the frequency band priority, seesection 4.2.5 "Multiband Direct Retry Based on UE Location" in Directed Retry DecisionFeature Parameter Description.

(e) When DRD for load balancing is enabled, the RNC selects the candidate cell with thelightest downlink load based on downlink load balancing. For a DC-HSDPA cell, the RNCconsiders the downlink load of the corresponding DC-HSDPA group, not the downlinkload of the DC-HSDPA cell. Therefore, the RNC selects at least two cells in the same DC-HSDPA group as candidate cells. Then, the RNC selects the cell with the lightest load asthe primary cell based on uplink load balancing and proceeds to step 3.

For details about how to select cells based on downlink load balancing, see DownlinkLoad-based Cell Selection. For details about how to select cells based on uplink loadbalancing, see Uplink Load-based Cell Selection.

3. The RNC selects the other cell in the DC-HSDPA group to which the primary cell belongsas the secondary cell. The DRD procedure is complete. Then, the RNC performs calladmission control (CAC). For details, see section 4.2.1 "Inter-Frequency DRD" in DirectedRetry Decision Feature Parameter Description.



26

NOTE

The HSPA technological satisfaction of DC-HSDPA cells is the same as that of SC-HSDPA cells. Whenall of the preceding DRD functions are disabled, the RNC instructs the UE to access the cell with the highestHSPA technological satisfaction. If the access fails, the RNC randomly selects a cell from candidate cellsfor the UE. If the cell supports DC-HSDPA, the cell serves as the primary cell, and the other cell in theDC-HSDPA group serves as the secondary cell. If the cell does not support DC-HSDPA, the UE accessesthe cell with the highest technology supported by the cell.

Service Priority-based Cell SelectionThe service priority-based cell selection for DC-HSDPA UEs is the same as the target cellselection for SC-HSDPA UEs.

When multiple candidate cells support the same HSPA+ technologies, the RNC determines theservice priorities of cells based on the uplink and downlink service bearers for the UE if DRDfor service steering is enabled. The RNC then ranks candidate cells according to service priorityand selects the cell with the highest service priority as the candidate cell.

The RNC uses HSDPA as the downlink service bearer for DC-HSDPA UEs.

If the requested service is combined services, the RNC uses the RAB with the highest priorityfor ranking. In addition, the selected cell must support all services in the combined services. Fordetails about the priority of a RAB, see Load Control Feature Parameter Description.

For details about how to select cells based on the service priority, see section 4.2.4 "Inter-Frequency DRD for Service Steering" in Directed Retry Decision Feature ParameterDescription.

Downlink Load-based Cell SelectionThe DRD for load balancing function for DC-HSDPA UEs is performed based on the numberof power resources available in the downlink and is basically the same as the downlink loadbalancing-based DRD for SC-HSDPA UEs. The only difference is that the RNC considers theload of the DC-HSDPA group to which the candidate cell belongs when performing DRD basedon load balancing for DC-HSDPA UEs.

For details about the downlink load balancing-based DRD, see section 4.2.6 "Inter-FrequencyDRD for Load Balancing" in Directed Retry Decision Feature Parameter Description.

Uplink Load-based Cell SelectionDC-HSDPA UEs have uplink channels only in the primary cell. If a large number of DC-HSDPAUEs use a cell as the primary cell, the uplink load of the cell increases, and the uplink coveragedeteriorates. The uplink load-based cell selection function helps balance the uplink load betweentwo carriers.

l If the uplink load balancing switch ULLdbDRDSwitchDcHSDPA is set to OFF, the RNCrandomly selects a cell from candidate cells as the primary cell.

l If this switch is set to ON, the RNC selects the cell with the lightest uplink load as thecandidate primary cell.

The RNC performs the uplink load balancing between candidate cells based on the equivalentnumber of users (ENUs) in the uplink.

The uplink load balancing-based DRD for DC-HSDPA is as follows:



27

1. If the UE initiates an RRC connection request in a non-candidate cell, the RNC selects thecell with the lightest uplink load from candidate cells as the primary cell.

2. In other circumstances, the RNC checks whether the remaining uplink ENUs of the currentcell are greater than the value of the ULLdbDRDLoadRemainThdDCHSDPA parameter.

l If the remaining uplink ENUs of the current cell are greater than the value of theULLdbDRDLoadRemainThdDCHSDPA parameter, the RNC selects the current cell asthe primary cell.

l If the remaining uplink ENUs of the current cell are less than or equal to the value of theULLdbDRDLoadRemainThdDCHSDPA parameter, the RNC calculates the differencebetween the remaining uplink ENUs of the candidate primary cell and that of the currentcell.– If the difference is greater than the value of ULLdbDRDOffsetDcHSDPA, the RNC

selects the candidate primary cell as the primary cell.– Otherwise, the RNC selects the current cell as the primary cell.

After selecting the primary cell, the RNC selects the other cell in the same DC-HSDPA groupas the secondary cell.

4.5.2 Call Admission Control

OverviewIn terms of Call Admission Control (CAC) based on the code resource, CE resource, or Iubresource, 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-HSDPACAC is changed, that is, the resources of the DC-HSDPA cell group need to be considered.

CAC Based on the DL PowerFigure 4-2 shows the resource allocation in the two cells of a DC-HSDPA cell group. In thisfigure, the DL power is taken as an example.

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



28

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

l Pmax: maximum DL power of a cell

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

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

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

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

For a non-DC-HSDPA UE, the RNC performs CAC based on the total DL power of the servingcell minus the DL power used for the existing non-DC-HSDPA UEs in this cell. If the admissionis successful, the RNC continues to perform the CAC based on the total DL power margin ofthe 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 DLpower.

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

For a non-DC-HSDPA UE, the RNC first performs CAC based on the ENU of the serving cell.If the admission is successful, the RNC then continues to perform the CAC based on the ENUof the DC-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.The DC-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.

For DC-HSDPA services, the RNC selects the primary cell in the DC-HSDPA cell group toperform preemption.

4.5.4 Load Reshuffling and Overload ControlThe power resources of a DC-HSDPA group may be in the basic congestion or overload state.Basic congestion is triggered when the sum of non-HSPA user power and HSPA user GBP ofthe two cells is greater than or equal to the sum of the downlink LDR trigger thresholds for thetwo cells. Overload is triggered when the sum of non-HSPA user power and HSPA user GBPof the two cells is greater than or equal to the sum of the downlink OLC trigger thresholds forthe two cells.



29

NOTE

l GBP: Guaranteed Bit rate Power

l LDR: load reshuffling

l OLC: overload control

If a DC-HSDPA group is in the basic congestion or overload state, both cells in the DC-HSDPAgroup are in the basic congestion or overload state. Under this condition, the RNC performs loadreshuffling or overload control to relieve the congestion or overload. For details about loadreshuffling and overload control, see sections "LDR Actions" and "OLC Actions" in LoadControl Feature Parameter Description, respectively.

The LDR and OLC for SC-HSDPA and R99 users are always the same, no matter whether theyare in DC-HSDPA cells or non-DC-HSDPA cells.

When LDR is implemented through load-based inter-frequency handovers, the target cell cannotbe a secondary cell of a DC-HSDPA UE if the RNC performs LDR on the DC-HSDPA UE.Other LDR actions are the same as those before the DC-HSDPA feature is applied. For details,see Load Control Feature Parameter Description.

DC-HSDPA+MIMO applies the same principles as DC-HSDPA in load control.

4.6 SchedulingThe NodeB selects the first cell from the two cells to perform the scheduling process. If the firstcell cannot 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 UEsin this cell.

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

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

l For SC-HSDPA, R represents the throughput corresponding to the CQI reported by the UEfor this carrier, and r represents the throughput currently achieved by the UE. A greater R/r value indicates a higher scheduling priority.

l For DC-HSDPA, R represents the throughput corresponding to the CQI reported by the UEfor this carrier, and r represents the total throughput currently achieved by the UE on thetwo carriers. A greater R/r value indicates a higher scheduling priority.

Scheduling in this way ensures the throughput fairness among DC-HSDPA users and SC-HSDPA users if they are in the same channel environments. The throughput of DC-HSDPAusers is slightly higher than that of SC-HSDPA users because DC-HSDPA users can bescheduled in the carrier with higher CQI of the two carriers.

If DC-HSDPA users are expected to have a higher throughput than SC-HSDPA users, you canapply the differentiated service policy. For details, see Differentiated HSPA Service FeatureParameter Description.



30

DC-HSDPA+MIMO applies the same principles as DC-HSDPA in scheduling. The TFRCalgorithm used by DC-HSDPA+MIMO is the same as that used by MIMO. For details, seeMIMO Feature Parameter Description.



31

5 Related Features

5.1 WRFD-010696 DC-HSDPA

Prerequisite Features

l WRFD-010610 HSDPA Introduction Package

l WRFD-010629 DL 16QAM Modulation

l WRFD-010685 Downlink Enhanced L2

DC-HSDPA must be enabled together with the WRFD-010683 Downlink 64QAM feature toprovide the single-user downlink peak throughput of 42 Mbit/s.

Mutually Exclusive Features

DC-HSDPA is mutually exclusive with the WRFD-021308 Extended Cell Coverage up to200km feature.

Impacted Features

DC-HSDPA is affected by the following features:

l WRFD-010617 VoIP over HSPA/HSPA+

– DC-HSDPA cannot be used for voice over IP (VoIP) services.

– DC-HSDPA can be used for combined VoIP+PS BE or VoIP+streaming services.

l WRFD-010619 CS voice over HSPA/HSPA+

– DC-HSDPA cannot be used for CS services.

– DC-HSDPA can be used for combined CS+PS BE or CS+streaming services

l WRFD-020134 Push to Talk

– DC-HSDPA cannot be used for push to talk (PTT) services.

– DC-HSDPA can be used for combined PTT+PS BE or PTT+streaming services.

WCDMA RANDC-HSDPA Feature Parameter Description 5 Related Features


32

l WRFD-160103 Terminal Black ListWhen the WRFD-160103 Terminal Black List feature is enabled, blacklisted users areprohibited from using DC-HSDPA.

DC-HSDPA affects the following features:

l WRFD-140217 Inter-Frequency Load Balancing Based on Configurable Load ThresholdWhen the number of DC-HSDPA UEs and their traffic volume are small, DC-HSDPA doesnot affect the Inter-Frequency Load Balancing Based on Configurable Load Thresholdfeature.When the number of DC-HSDPA UEs and their traffic volume are large, the gain providedby the Inter-Frequency Load Balancing Based on Configurable Load Threshold featuredecreases. The reason is as follows: DC-HSDPA uses joint scheduling to balance the loadacross different carriers. The load balancing effect depends on the number of DC-HSDPAUEs and the traffic volume. When the number of DC-HSDPA UEs and the traffic volumeare large, the load balancing effect is noticeable, but the gain provided by the Inter-Frequency Load Balancing Based on Configurable Load Threshold feature decreases.

l WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback PeriodDC-HSDPA can be used with the Dynamic Configuration of HSDPA CQI Feedback Periodfeature.When these two features are used together, the gain (RTWP reduction) provided by theDynamic Configuration of HSDPA CQI Feedback Period feature slightly increases,compared with when SC-HSDPA and Dynamic Configuration of HSDPA CQI FeedbackPeriod are used together. The uplink CQI feedback overhead for DC-HSDPA is slightlygreater than that for SC-HSDPA, so the received total wideband power (RTWP) of DC-HSDPA is higher than that of SC-HSDPA. The Dynamic Configuration of HSDPA CQIFeedback Period feature helps reduce the RTWP.

l WRFD-021304 RAN Sharing Introduction Package, WRFD-021305 RAN Sharing Phase2, and WRFD-021311 MOCN Introduction PackageIn RAN sharing and MOCN scenarios, the RNC determines whether to use cells belongingto different operators for HSDPA transmission of a DC-HSDPA UE based on the parametersettings.

l WRFD-010689 HSPA+ Downlink 42Mbps per UserAfter DC-HSDPA is introduced, the HSPA+ Downlink 42Mbps per User feature candepend on the following feature: WRFD-010696 DC-HSDPA.

5.2 WRFD-010699 DC-HSDPA+MIMO

Prerequisite Featuresl WRFD-010696 DC-HSDPAl WRFD-010684 2x2 MIMO

For details on how to activate the WRFD-010684 2x2 MIMO feature, see chapter 12"Engineering Guidelines" in MIMO Feature Parameter Description.

Mutually Exclusive FeaturesNone



33

Impacted FeaturesThe WRFD-010703 HSPA+ Downlink 84Mbit/s per User feature depends on DC-HSDPA+MIMO. In addition, to achieve the single-user downlink peak throughput of 84 Mbit/s, DC-HSDPA+MIMO must be used together with the WRFD-010683 Downlink 64 QAM feature.



34

6 Network Impact


System Capacity

DC-HSDPA provides the following benefits:

l Increases single-user downlink peak throughput. DC-HSDPA together with 64QAMpushes the single-user downlink peak throughput up to 42 Mbit/s.

l Reduces the transmission delay of burst services and improves user experience.

DC-HSDPA UEs have the HS-DPCCH only in the primary cell, and therefore the uplink loadof the primary cell is slightly higher than that of SC-HSDPA cells.

DC-HSDPA UEs consume one channel element (CE) more than SC-HSDPA UEs.

Network Performance

DC-HSDPA affects cell uplink load and cell downlink load.

l Impact on cell uplink load

Compared with SC-HSDPA UEs, DC-HSDPA UEs need to demodulate the signals in theprimary and secondary cells and need to report the feedback about both cells in the primarycell. The transmit power of a DC-HSDPA UE on the HS-DPCCH is about 2 dB higher thanthat of an SC-HSDPA UE. Theoretically, the uplink load of a DC-HSDPA UE in theprimary cell is about 0.2% higher than that of an SC-HSDPA UE. When the penetrationrate of DC-HSDPA UEs is small, this feature has little impact on network performance.

l Impact on cell downlink load

– For cells that have the same HSDPA service priority, DC-HSDPA does not significantlyaffect the downlink load.

– For cells that have different HSDPA service priorities, DC-HSDPA increases thedownlink load of the cell with lower HSDPA service priority. The load increase isrelated to the proportion of UEs supporting DC-HSDPA and service model.

WCDMA RANDC-HSDPA Feature Parameter Description 6 Network Impact


35


System CapacityDC-HSDPA+MIMO provides the following benefits:

l Increases single-user downlink peak throughput. DC-HSDPA+MIMO increases the single-user downlink throughput by about 100% compared with SC-HSDPA+MIMO. Theincrease in the single-user downlink throughput is noticeable even at the cell edge.However, the increase in the single-user downlink throughput varies depending on the loadof other DC-HSDPA+MIMO cells in the same sector. For example, when other DC-HSDPA+MIMO cells in the same sector have heavy loads, the gain provided by DC-HSDPA+MIMO is small.

l Reduces the transmission delay of burst services and improves user experience.

DC-HSDPA+MIMO UEs consume one CE more than SC-HSDPA+MIMO UEs.

A baseband processing board supports more SC-HSDPA+MIMO UEs than DC-HSDPA+MIMO UEs.

Network Performancel Slightly increases the cell load in the uplink. The cell load increase is represented by an

increase in the uplink RTWP. The increase in the uplink RTWP varies depending on thenumber of online DC-HSDPA+MIMO UEs. When the number of online DC-HSDPA+MIMO UEs increases, the HS-DPCCH has more data to transmit in the uplink andconsequently requires more power resources. Uplink interference increases as a result.

l Deteriorates uplink cell edge coverage. DC-HSDPA+MIMO slightly deteriorates theuplink cell edge coverage because DC-HSDPA+MIMO UEs need to report the CQIinformation about both serving cells and consequently require higher uplink power.

l For details about the impacts on downlink cell load, see Network Performance.

WCDMA RANDC-HSDPA Feature Parameter Description 6 Network Impact


36

7 Engineering Guidelines


7.1.1 When to Use DC-HSDPADC-HSDPA applies to operators who have at least two frequencies at the same frequency band.

It is recommended that DC-HSDPA be deployed in urban areas. In the busy time, user-selectivescheduling and load balancing of DC-HSDPA increases capacity. In the spare time, DC-HSDPAincreases maximum user throughput and reduces delay.

DC-HSDPA can be deployed in suburban areas or rural areas. It improves user overall experienceand significantly improves the edge users' experience.

In urban areas where the network capacity is not limited, DC-HSDPA provides more benefitsif most services on the live network are burst services. Details are as follows:

Compared with SC-HSDPA, DC-HSDPA doubles the single-user throughput in the cell centerand at the cell edge. DC-HSDPA also reduces the transmission delay and improves userexperience. However, when the number of UEs performing data transmission increases, thedownlink load increases, and as a result the feature benefits in single-user throughput and cellthroughput decrease.

DC-HSDPA can also be deployed in networks with limited capacity and high downlink load(for example, the average downlink transmit power is greater than 80% for a long time), but thefeature benefits are less noticeable.

7.1.2 Required InformationBefore feature deployment, operators need to collect the following information:

l Proportion of UEs supporting DC-HSDPA

A higher proportion of UEs supporting DC-HSDPA results in better system throughput gains.

The VS.HSDPA.UE.Mean.CAT21.24 and VS.HSDPA.UE.Mean.CAT25.28 counters measurethe average numbers of DC-HSDPA UEs.

WCDMA RANDC-HSDPA Feature Parameter Description 7 Engineering Guidelines


37

l Uplink capabilities

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

For details about how to check whether HSUPA is enabled in the uplink, see HSUPA FeatureParameter Description.

l Bandwidth over the Iub interface

If the bandwidth over the Iub interface is inadequate, DC-HSDPA cannot yield no gains. Anappropriate bandwidth is required over the Iub interface.

DC-HSDPA provides single-user downlink peak throughput of 42 Mbit/s. The minimumbandwidth over the Iub interface is 50 M in IP transmission and is 55 M in ATM transmissionconsidering the Iub transmission efficiency. The actual bandwidth required over the Iub interfaceis greater than 50 M because there are R99 users on the live network. The actual bandwidthrequired over the Iub interface must be calculated based on network planning and networkoptimization.

l Packet loss rate on the core network

If the core network has a high packet loss rate, gains provided by DC-HSDPA decrease duringsingle-thread FTP sessions. An appropriate packet loss rate is required for the core network.

The recommended packet loss rate over the Iu interface is less than one of a million.

l Downlink cell load

If the downlink loads of cells in the same sector exceed 85% for most of the time, the benefitsprovided by DC-HSDPA may decrease.

The VS.MeanTCP counter measures the downlink load of a cell.

7.1.3 PlanningDC-HSDPA sets the following requirements on NodeB hardware:

l For 3900 series base stations, the BBU3900 needs to be configured with the WBBPb,WBBPd, UBBP, or WBBPf board.

l For the DBS3800, the BBU3806 needs to be configured with the EBBC or EBBCd board.l The BTS3812AE or BTS3812E needs to be configured with the EBBI, EDLP, or EDLPd

board, and the UL baseband resources of DC-HSDPA cells cannot be carried on the HBBIor HULP board. They need to be carried on the EBBI, EULP, or EULPd board.

Table 7-1 presents an example of the hardware configuration of a NodeB that is configured withthree sectors, with two carriers in each sector.

Table 7-1 Example of the hardware configuration of a NodeB that is configured with threesectors (with two carriers in each sector)

Base Station Type Hardware Configuration

3900 series basestations

Each 3900 series base station must be configured with one WBBPb,one WBBPd, one UBBP, or one WBBPf board.



38

Base Station Type Hardware Configuration

DBS3800 The DBS3800 must be configured with one EBBC or one EBBCdboard.

BTS3812AE andBTS3812E

Each NodeB of these types must be configured either with oneEDLP board and one EULP or EULPd board or with one EBBIboard.

7.1.4 DeploymentThis section describes how to activate, verify, and deactivate the optional feature WRFD-010696DC-HSDPA.

7.1.4.1 Requirementsl Other Features

The cells to be enabled with DC-HSDPA must have the prerequisite features enabled. Fordetails about the prerequisites features for DC-HSDPA, see section PrerequisiteFeatures.

l License

The license "The number of Cells with DL DC function enabled" on the NodeB side hasbeen activated. For details about how to activate the license, see License ManagementFeature Parameter Description.

Feature ID FeatureName

LicenseControl Item

NE Sales Unit

WRFD-010696

DC-HSDPA The number ofCells with DLDC functionenabled

NodeB per Cell

l Others

– One local cell can belong to only one DC-HSDPA group.

– The two DC-HSDPA cells must belong to the same baseband board.

– The two DC-HSDPA cells must belong to the same sector.

– The two DC-HSDPA cells of a DC-HSDPA group are in the same downlink resourcegroup of a NodeB.

After the configuration of DC-HSDPA cell group, the NodeB tries to set up all the cellsin the DC-HSDPA cell group in the same board. If not all the cells are set up in the samegroup, the NodeB reports ALM-28206 Local Cell Capability Decline.

– For distributed cells, two local cells in a DC-HSDPA cell group must belong to oneRRU. For non-distributed cells, if two local cells in a DC-HSDPA cell group belong totwo RRUs, the RRUs adopt a star or chain topology.

– The RNC software version is RAN12.0 or later.



39

– The NodeB software version is RAN12.0 or later.

– When the two DC-HSDPA cells of a DC-HSDPA group operate on adjacentfrequencies, the difference between the values of the UARFCNDownlink parametersfor the two cells must be greater than 19 and meanwhile less than or equal to 25. Whenthe two DC-HSDPA cells of a DC-HSDPA group operate on non-adjacent frequencies,the difference between the values of the UARFCNDownlink parameters for the twocells must be an integer multiple of 25.

– UEs must belong to HS-DSCH category 21 or higher. For details, see 3.5 UECategories.

7.1.4.2 Data Preparation

Table 7-2 and Table 7-3 list the data to prepare before activating DC-HSDPA.

Table 7-2 NodeB data to prepare before activating DC-HSDPA

Parameter Name Parameter ID Setting Notes DataSource

Multiple Carrier CellGroup Type

multiCellGrpType

This parameter must be set toHSDPA(HSDPA).

Engineeringdesign

Multiple Carrier CellGroup ID

multiCellGrpId Cells in a sector should be addedto the same multi-carrier cellgroup.The multi-carrier cell group IDmust be unique under a NodeB.

Engineeringdesign

Local Cell ID uLoCellId Cells in the same multi-carriercell group must meet therequirements described in section3.2.2 Multi-Carrier CellGroups.

Radionetworkplan(internal)

Table 7-3 RNC data to prepare before activating DC-HSDPA

ParameterName

Parameter ID Setting Notes Data Source

NodeBProtocolVersion

NodeBProtclVer

It is recommended that this parameter beset to R9.

Radio networkplan (internal)

CN domainID

CNDomainId Set this parameter to PS_DOMAIN. Radio networkplan (internal)

CNprotocolversion

CNProtclVer It is recommended that this parameter beset to R8.




40

ParameterName

Parameter ID Setting Notes Data Source

Time Offset TCell All cells in the same sector that are to beenabled with DC-HSDPA must have thisparameter set to the same value.


ChannelConfiguration StrategySwitch

CfgSwitch CFG_HSDPA_DC_SWITCH in theCfgSwitch parameter must be selected.


PreferredMIMO_64QAM orDC_HSDPA Character

MIMO64QA-MorDcHSDPASwitch

DC-HSDPA in the MIMO64QA-MorDcHSDPASwitch parameter mustbe selected.This parameter specifies priorities forMIMO+64QAM and DC-HSDPA. If thenetwork supports both MIMO+64QAMand DC-HSDPA, consult with theoperator to determine which techniquetakes priority. If the network load isheavy, set this parameter to MIMO+64QAM. Otherwise, set this parameterto DC-HSDPA.


ServiceMappingStrategySwitch

MapSwitch If streaming services need to be carriedon HSDPA,MAP_PS_STREAM_ON_HSDPA_SWITCH in the MapSwitch parametermust be selected.


Cell HspaPlusfunctionswitch

HspaPlusSwitch

DC_HSDPA(Cell DC-HSDPAFunction Switch) andDL_L2ENHANCED(Cell DLL2ENHANCED Function Switch) inthe HspaPlusSwitch parameter must beselected.


HSPATechnologies Retriedby UEs

RetryCapability When DRD needs to be enabled for DC-HSDPA UEs, DC_HSDPA in theRetryCapability parameter must beselected.


7.1.4.3 Precautions

Activate this feature when the traffic volume in a cell is low. The reason is that the cell must bedeactivated before this feature is activated; after the cell is deactivated, the services in this cellare interrupted.

7.1.4.4 Activation



41

7.1.4.4.1 Using MML Commands

Step 1 Change the NodeB's and CN's protocol versions to versions that support DC-HSDPA.

NOTE

3GPP Release 8 and later support DC-HSDPA. It is recommended that the NodeB's protocol version beset to Release 9 and that the CN's protocol version be set to Release 8.

1. Run the RNC MML command MOD UNODEB to set NodeB Protocol Version to R9.

2. Run the RNC MML command MOD UCNNODE to set CN domain ID toPS_DOMAIN and set CN protocol version to R8.

Step 2 Run the RNC MML command DEA UCELL multiple times to deactivate each logical cell ofthe cells to be enabled with DC-HSDPA. It is recommended that all cells under a NodeB bedeactivated, including SC-HSDPA cells

NOTE

Deactivating a cell interrupts the ongoing services in the cell. Therefore, it is recommended that the celldeactivation operation be performed in low traffic hours, for example, in the early morning.

Step 3 Run the NodeB MML command MOD ULOCELL to modify the value of the Cell ScaleIndication parameter.

NOTE

Compared with activating the DC-HSDPA feature, activating the Macro-Micro DC-HSDPA featurerequires an additional step: configuring a cell as a macro or micro cell. If it is not for Macro-Micro DC-HSDPA, omit this step.

Step 4 Run the NodeB MML command ADD NODEBMULTICELLGRP to add a multi-carrier cellgroup.

NOTE

The multi-carrier cell group ID must be unique under a NodeB.

The multi-carrier cell group ID can be queried using the NodeB MML command LSTNODEBMULTICELLGRP.

Step 5 Run the NodeB MML command ADD NODEBMULTICELLGRPITEM multiple times toadd the cells to the multi-carrier cell group.

NOTE

Only the cells that meet the requirements described in section Multi-Carrier Cell Groups can be added toa multi-carrier cell group.

Step 6 Run the NodeB MML command STR REALLOCLOCELL to start the reestablishment of alllocal cells based on baseband resource optimization.

NOTE

Running this command interrupts the ongoing services in all cells under the NodeB. Therefore, it isrecommended that this command be executed in low traffic hours, for example, in the early morning.

Step 7 (Optional) Run the RNC MML command MOD UCELLSETUP to modify the value of theTime Offset parameter based on the prepared data.

NOTE

Step 4 is required only when the value of the Time Offset parameter is inconsistent between DC-HSDPAcells. The value of the Time Offset parameter can be queried using the RNC MML command LSTUCELL.



42

Step 8 After configuring all the multi-carrier cell groups under a NodeB, run the RNC MML commandACT UCELL multiple times to activate the cells in the multi-carrier cell group.

Step 9 Run the RNC MML command SET UCORRMALGOSWITCH to turn on the DC-HSDPAbearing switch by selecting CFG_HSDPA_DC_SWITCH in the Channel ConfigurationStrategy Switch parameter.

Step 10 Run the RNC MML command SET UFRC to select DC-HSDPA as the preferential HSPA+technology by selecting DC_HSDPA in the Preferred MIMO_64QAM or DC_HSDPACharacter parameter.

NOTE

Select DC_HSDPA in the Preferred MIMO_64QAM or DC_HSDPA Character parameter beforefeature verification. If the planned HSPA+ technology for a cell is not DC-HSDPA, select the plannedHSPA+ technology as required after feature verification.

Step 11 (Optional) If streaming services need to use DC-HSDPA, run the RNC MML command SETUCORRMALGOSWITCH to select MAP_PS_STREAM_ON_HSDPA_SWITCH underthe Service Mapping Strategy Switch parameter.

Step 12 Run the RNC MML command MOD UCELLALGOSWITCH multiple times to enable DC-HSDPA by selecting DC_HSDPA(Cell DC-HSDPA Function Switch) under the Cell HspaPlus function switch parameter.

Step 13 (Optional) When DC-HSDPA DRD is required, run the RNC MML command SET UFRC toenable DC-HSDPA DRD by selecting DC_HSDPA under the HSPA Technologies Retried byUEs parameter.

----End

7.1.4.4.2 MML Command Examples//RNC Operation//Modifying NodeB's and CN's protocol versionsMOD UNODEB: IDTYPE=BYID, NodeBId=1, NodeBProtclVer=R9;MOD UCNNODE: CnOpIndex=0, CNId=0, CNDomainId=PS_DOMAIN, CNProtclVer=R8;//Deactivating local cellsDEA UCELL: CellId=1;DEA UCELL: CellId=2;//NodeB Operation//Setting Cell1 to a micro cellMOD ULOCELL: uLOCELLId=1, SECT=LOCAL_SECTOR, CELLSCALEIND=Micro;//Adding local cells to a specified multi-carrier cell groupADD NODEBMULTICELLGRP: multiCellGrpId=1, multiCellGrpType=HSDPA;ADD NODEBMULTICELLGRPITEM: multiCellGrpId=1, uLoCellId=1;ADD NODEBMULTICELLGRPITEM: multiCellGrpId=1, uLoCellId=2;//Starting the reestablishment of all local cells based on baseband resource optimizationSTR REALLOCLOCELL:;//RNC Operation//Modifying the time offset parameter for a cellMOD UCELLSETUP: CellId=1, TCell=CHIP512;//Reactivating local cellsACT UCELL: CellId=1;ACT UCELL: CellId=2;//Setting the DC-HSDPA bearing switch to onSET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DC_SWITCH-1;//Setting the preferential HSPA+ technology for a cell to DC-HSDPASET UFRC: MIMO64QAMorDcHSDPASwitch=DC_HSDPA;//Setting the service mapping strategy switchSET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-1;//Setting the DC-HSDPA switch for cells to on



43

MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DC_HSDPA-1;MOD UCELLALGOSWITCH: CellId=2, HspaPlusSwitch=DC_HSDPA-1;//Enabling DC-HSDPA DRDSET UFRC: RetryCapability=DC_HSDPA-1;

7.1.4.4.3 Using the CME

NOTE

When configuring the DC-HSDPA feature on the CME, perform a single configuration first, and thenperform a batch modification if required.

Configure the parameters of a single object before a batch modification. Perform a batch modificationbefore logging out of the parameter setting interface.

Step 1 Configure a single object (such as a cell) on the CME.

Set parameters on the CME according to the operation sequence in Table 7-4. For instructionson how to perform the CME single configuration, see CME Single Configuration OperationGuide.

Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)

----End

To modify objects in batches, click on the CME to start the batch modification wizard. Forinstructions on how to perform a batch modification through the CME batch modification center,press F1 on the wizard interface to obtain online help.

Table 7-4 Configuring parameters on the CME

SN MO NE ParameterName

Parameter ID

Configurable inCMEBatchModificationCenter

1 UNODEB RNC NodeB ProtocolVersion (Setthis parameterto R9.)

NodeBProtclVer

No

UCNNODE RNC CN domain ID(Set thisparameter toPS_DOMAIN.)

CNDomainId

No

CN protocolversion (Set thisparameter toR8.)

CNProtclVer



44


Parameter ID


2 UCELL RNC Validationindication (Setthis parametertoDeactivated.)

ACTSTATUS

Yes

3 ULOCELL NodeB

Cell ScaleIndication

CELLSCALEIND

Yes

4 NodeBMultiCellGrp NodeB

Multiple CarrierCell Group ID

multiCellGrpId

Yes

Multiple CarrierCell GroupType

multiCellGrpType

5 LocellIdListTypeNOTE

Add local cells to themulti-carrier cell groupconfigured in step 2.

NodeB

Local Cell ID uLoCellId

No

6(Optional)

UCELLNOTE

Step 4 is required onlywhen the value of theTime Offset parameter isinconsistent between DC-HSDPA cells.

RNC Cell ID CellId Yes

Time Offset TCell

7 UCELL RNC Validationindication (Setthis parameterto Activated.)

ACTSTATUS

Yes

8 UCORRMALGOSWITCH

RNC ChannelConfigurationStrategy Switch

CfgSwitch

Yes



45


Parameter ID


9 UFRCNOTE

Select DC-HSDPA in thePreferredMIMO_64QAM orDC_HSDPA Characterparameter before featureverification. If the plannedHSPA+ technology for acell is not DC-HSDPA,select the planned HSPA+technology as requiredafter feature verification.

RNC PreferredMIMO_64QAM orDC_HSDPACharacter

MIMO64QAMorDcHSDPASwitch

Yes

10(Optional)

UCORRMALGOSWITCHNOTE

If streaming services needto be carried on HSDPA,selectMAP_PS_STREAM_ON_HSDPA_SWITCH inthe Service MappingStrategy Switchparameter.

RNC ServiceMappingStrategy Switch

MapSwitch

Yes

11 UCELLALGOSWITCH RNC Cell Hspa Plusfunction switch

HspaPlusSwitch

Yes

12(Optional)

UFRCNOTE

This step is required whenDC-HSDPA DRD needsto be enabled.

RNC HSPATechnologiesRetried by UEs

RetryCapability

Yes

7.1.4.5 Activation Observation

Monitor counters or trace signaling to check whether DC-HSDPA is working properly.

Monitoring Counters

Monitor the value of the VS.HSDPA.RAB.DC.SuccEstab counter for DC-HSDPA cells. If thevalue of this counter is not zero for a DC-HSDPA cell, DC-HSDPA is working properly for thatcell.



46

Tracing Signaling

Step 1 Click Uu Interface Trace on the LMT, as shown in Figure 7-1.

Figure 7-1 Uu Interface Trace dialogue box

Step 2 For cells with Cell DC-HSDPA Function Switch turned on, trace RRC_RB_SETUP messageson the Uu interface.

Step 3 Perform dialing tests on FTP services for a UE to ensure that data is transmitted on HSDPAchannels.

Step 4 On the Trace tab page of the LMT, check whether RRC_RB_SETUP messages contain thedl-SecondaryCellInfoFDD information element.

----End

l If the dl-SecondaryCellInfoFDD information element is contained, as shown in Figure7-2, it indicates that the feature is activated.

l If the dl-SecondaryCellInfoFDD information element is not contained, it indicates thatthe feature is not activated.



47

Figure 7-2 RRC_RB_SETUP message

7.1.4.6 Deactivation


Step 1 Run the RNC MML command MOD UCELLALGOSWITCH to disable DC-HSDPA in a cellby deselecting DC_HSDPA(Cell DC-HSDPA Function Switch) in the Cell Hspa Plusfunction switch parameter.

Step 2 Run the RNC MML command SET UCORRMALGOSWITCH to set the DC-HSDPA bearingswitch to off by deselecting CFG_HSDPA_DC_SWITCH in the Channel ConfigurationStrategy Switch parameter.

Step 3 Run the NodeB MML command RMV NODEBMULTICELLGRPITEM to remove DC-HSDPA cells from the multi-carrier cell group.

Step 4 Run the NodeB MML command RMV NODEBMULTICELLGRP to remove the multi-carriercell group.

----End

7.1.4.6.2 MML Command Examples//Disabling DC-HSDPAMOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DC_HSDPA-0;MOD UCELLALGOSWITCH: CellId=2, HspaPlusSwitch=DC_HSDPA-0;SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DC_SWITCH-0;//Removing DC-HSDPA cells from the multi-carrier cell groupRMV NODEBMULTICELLGRPITEM: multiCellGrpId=1, uLoCellId=1;RMV NODEBMULTICELLGRPITEM: multiCellGrpId=1, uLoCellId=2;RMV NODEBMULTICELLGRP: multiCellGrpId=1, multiCellGrpType=HSDPA;

7.1.4.6.3 Using the CME

NOTE

When configuring the DC-HSDPA feature on the CME, perform a single configuration first, and thenperform a batch modification if required. Configure the parameters of a single object before a batchmodification. Perform a batch modification before logging out of the parameter setting interface.

Step 1 Configure a single object (such as a cell) on the CME.

Set parameters on the CME according to the operation sequence in Table 7-5. For instructionson how to perform the CME single configuration, see CME Single Configuration OperationGuide.

Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)

----End



48

To modify objects in batches, click on the CME to start the batch modification wizard. Forinstructions on how to perform a batch modification through the CME batch modification center,press F1 on the wizard interface to obtain online help.

Table 7-5 Configuring parameters on the CME


ParameterID

Configurable in CMEBatchModification Center

1 UCORRMALGOSWITCH

RNC ChannelConfiguration StrategySwitch

CfgSwitch Yes

2 LocellIdListType

NodeB Local cell ID uLoCellId No

3 NodeBMultiCellGrp

NodeB MultipleCarrier CellGroup ID

multiCellGrpId

Yes

MultipleCarrier CellGroup Type

multiCellGrpType

7.1.5 Performance Monitoring

7.1.5.1 Monitoring Counters

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

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

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

l VS.HSDPA.DC.PRIM.UE.Mean.Cell: average number of users that have chosen thecurrent cell as the primary cell

l VS.HSDPA.DC.SEC.UE.Mean.Cell: average number of users that have chosen the currentcell as the secondary cell

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

l VS.HSDPA.DCCfg.AnchorCarrierActedNum: number of times during a measurementperiod that the current cell has performed scheduling for users that are configured with DC-



49

HSDPA and have chosen the current cell as the primary cell, regardless of whether thesecondary carrier has performed scheduling simultaneously. If the primary and secondarycarriers have performed scheduling for a user simultaneously, only one time is counted.

l VS.HSDPA.DCCfg.SupCarrierActedNum: number of times during a measurement periodthat the current cell has performed scheduling for users that are configured with DC-HSDPA and have chosen the current cell as the secondary cell, regardless of whether theprimary carrier has performed scheduling at the same time. If the primary and secondarycarriers have performed scheduling for a user simultaneously, only one time is counted.

l VS.HSDPA.DCCfg.DualCarrierActedNum: number of times during a measurement periodthat scheduling has been performed by the primary and secondary carriers at the same timefor users that are configured with DC-HSDPA and have chosen the current cell as theprimary cell

DC-HSDPA increases cell throughput and peak rates for individual users.

To determine the average DC-HSDPA UE throughput, average cell HSDPA throughput, andtotal downlink throughput before and after DC-HSDPA is deployed, check the values of thefollowing counters:

l VS.DataOutput.DCHSDPA.Traffic: This counter measures the amount of traffic that iscorrectly transmitted for DC-HSDPA/DC-HSDPA+MIMO UEs at the MAC-ehs layer.This counter is in units of kbit/s.

l VS.DCHSDPA.DataTtiNum.User: This counter measures the number of TTIs duringwhich DC-HSDPA/DC-HSDPA+MIMO buffer queues have data to transmit. If multiplequeues have data to transmit in a TTI, the TTI number needs to be multiplied by the numberof queues that have data to transmit. This counter is measured only on the primary carrier.

Use the following formula to calculate the average throughput of DC-HSDPA UEs at theMAC-ehs layer under a NodeB:

Calculate the average throughput of DC-HSDPA UEs at the MAC-ehs layer under a NodeBbased on the following counters:

VS.HSDPA.MeanChThroughput: an RNC counter that measures the average downlinkthroughput 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 indrive tests.

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

7.1.5.2 Monitoring KPIs

The following cell-level KPIs indicate the performance of DC-HSDPA:

l DC-HSDPA RAB Setup Failure Rate = 1 - (VS.HSDPA.RAB.DC.SuccEstab/VS.HSDPA.RAB.DC.AttEstab) x 100%

After DC-HSDPA is enabled, this KPI measures the DC-HSDPA RAB setup failure rate.If the DC-HSDPA RAB setup failure rate is much greater than the SC-HSDPA RAB setupfailure rate, the proportion of UEs supporting DC-HSDPA may be very low or the DC-HSDPA traffic volume may be very small. Under either condition, the value of theVS.HSDPA.RAB.DC.AttEstab counter is small.



50

When the proportion of UEs supporting DC-HSDPA is very low or the DC-HSDPA trafficvolume is very small, this KPI cannot indicate the actual DC-HSDPA RAB setup failurerate.

l DC-HSDPA Call Drop Rate = VS.HSDPA.RAB.AbnormRel.DC/(VS.HSDPA.RAB.AbnormRel.DC+ VS.HSDPA.RAB.NormRel.DC) x 100%After DC-HSDPA is enabled, this KPI measures the DC-HSDPA call drop rate. If the DC-HSDPA call drop rate is much greater than the SC-HSDPA call drop rate, the proportionof UEs supporting DC-HSDPA may be very low or the DC-HSDPA traffic volume maybe very small. Under either condition, the value of the VS.HSDPA.RAB.DC.AttEstabcounter is small.When the proportion of UEs supporting DC-HSDPA is very low or the DC-HSDPA trafficvolume is very small, this KPI cannot indicate the actual DC-HSDPA call drop rate.

7.1.6 Parameter OptimizationN/A

7.1.7 TroubleshootingTable 7-6 lists the alarms related to DC-HSDPA.

Table 7-6 Alarms related to DC-HSDPA

Alarm ID Alarm Name NE Feature ID Feature Name

ALM-28206 Local CellCapabilityDecline

NodeB WRFD-010696 DC-HSDPA

ALM-22221 UMTS Cell DC-HSDPAFunction Fault

RNC WRFD-010696 DC-HSDPA


7.2.1 When to Use DC-HSDPA+MIMODC-HSDPA+MIMO combines the DC-HSDPA and MIMO technologies, and its performancegain is mainly provided by these two technologies.

With the DC-HSDPA technology, both carriers are used to transmit data in all scenarios. Thisincreases the data rate for most UEs, regardless of whether they are in the cell center or at thecell edge. In addition, this increases system capacity. The gain provided by the MIMOtechnology changes with the radio environment. MIMO is recommended in propagationenvironments with a high signal-to-noise ratio (SNR), for example, an environment withmultipath propagation and short delay.

Table 7-7 describes the characteristics of the application scenarios.



51

Table 7-7 Characteristics of the application scenarios

Scenario Description

Radio environment Multipath propagation Propagation paths are variousand transmission delay isshort.

User behavior Service model Most services are PSservices.

Mobility Most UEs stay still or moveslowly.

Traffic model A large proportion ofservices are high-speed dataservices.

UE distribution Most UEs are near theNodeB.

DC-HSDPA+MIMO is recommended in the following scenarios:

l Hot spots with Wi-Fi signals, for example, airports, commercial streets, and universitycampuses.

l Densely populated areas, for example, markets and shopping malls

l Residential areas. This feature can be deployed in these areas to replace DSL or cableInternet access.

7.2.2 Required Information

Geographical Environment

Ensure that the target area has various propagation paths and a short transmission delay.

UE Distribution

Obtain the UE distribution on the network. Ensure that most UEs stay still or move slowly. Todetermine UE mobility, view the RRC.AttConnEstab.Reg, VS.HHO.AttIntraFreq.RNC,and VS.HHO.AttInterFreq.RNC counters.

Ensure that most UEs stay near the NodeB. To determine the distance between UEs and theNodeB, view the measurement reports (MRs) or other messages that carry the distanceinformation. Ensure that most UEs mainly perform high-speed PS services. To determine theratio of high-speed PS services, view the mean throughput and traffic volume for each servicetype.

Traffic Volume

Ensure that the PS traffic volume is high in the network.



52

Number of CarriersEnsure that the operator has two or more frequencies and at least two of them are adjacent.

UE CategoriesEnsure that UEs of category 25, 26, 27, 28, 30, or 32 are available in the network.

If UEs in the network do not belong to the preceding categories, gains provided by DC-HSDPA+MIMO are insignificant.

7.2.3 Planning

7.2.3.1 RF PlanningEnsure that RF resources meet the following requirements:l The two frequencies are adjacent and the cells served by the two frequencies are under the

same sector and the same NodeB.l

l They must have the same time offset (specified by the Tcell parameter).

7.2.3.2 Network PlanningIn scenarios where two carriers are available and traffic steering is not applied, it is recommendedthat this feature be deployed as follows:

l Both carriers support R99+HSDPA+MIMO.l The two carriers are configured as a DC-HSDPA carrier group.

In scenarios where three carriers are available and R99 services are carried by a separate carrier,it is recommended that this feature be deployed as follows:

l One of the carriers supports only R99 services.l The other two carriers support HSDPA+MIMO and are configured as a DC-HSDPA carrier

group.

7.2.4 Deployment

7.2.4.1 Requirementsl Hardware

– The HBBI and HDLP boards in the BTS3812AE and BTS3812E do not support DC-HSDPA+MIMO. To support DC-HSDPA+MIMO, the BTS3812AE and BTS3812Emust be configured with the EBBI, EBOI, or EDLP board. When configured with theEDLP board, the BTS3812AE or BTS3812E must also be configured with the EULPor EULPd board.

NOTE

Operators can run the NodeB MML command DSP ULOCELLRES to check whether the celldownlink resources are established on the preceding boards.



53

– The DBS3800 must be configured with the EBBC or EBBCd board. In addition, theDBS3800 allows only one cell of the DC-HSDPA cell group to be configured withMIMO.

– The 3900 series base stations must be configured with the WBBPb, WBBPd, UBBP,or WBBPf board.

– For the BTS3812AE or BTS3812E, two WRFUs are interconnected to support MIMOin Primary/Secondary common Pilot (PSP) mode.

– MIMO requires two transmit channels. When RRUs with single transmit channels areused, for example, the RRU3804, two RRUs must be interconnected to support MIMO.When RRUs with two transmit channels are used, for example, the RRU3808, only oneRRU is required.

l Other Features

The cells to be enabled with DC-HSDPA+MIMO must have the prerequisite featuresenabled. The prerequisite features are WRFD-010696 DC-HSDPA and WRFD-0106842×2 MIMO.

l License

The license for this feature has been activated on the NodeB side. For details about how toactivate a license, see License Management Feature Parameter Description.

The following table lists the detailed information about the license.

Feature ID Feature Name License Control Item NE SalesUnit

WRFD-010699

DC-HSDPA+MIMO

The number of cells withDC-HSDPA+MIMOfunction enabled

NodeB Cell

l Others

The UE must belong to HS-DSCH category 25, 26, 27, or 28.

7.2.4.2 Data Preparation

None

7.2.4.3 Precautions

None

7.2.4.4 Activation


Step 1 To enable the algorithm switch for RNC-level DC-HSDPA+MIMO, run the RNC MMLcommand SET UCORRMALGOSWITCH (CME single configuration: UMTS Radio GlobalConfiguration Express > Connection_Oriented RRM Switch Configuration > ConnectionOriented Algorithm Switches; CME batch modification center: Modifying RNC Parametersin Batches). In this step, select CFG_HSDPA_DCMIMO_SWITCH and



54

CFG_HSDPA_MIMO_SWITCH check boxes under the Channel Configuration StrategySwitch parameter.

Step 2 (Optional) Run the RNC MML command SET UFRC (CME single configuration: UMTSRadio Global Configuration Express > Basic Resource Control ParameterConfiguration > RNC Oriented FRC Algorithm Parameters; CME batch modificationcenter: Modifying RNC Parameters in Batches) and set the following parameters:l Select the DC_HSDPA_MIMO check box under the DC-HSDPA+MIMO or 4C-HSDPA

Preferential Switch parameter to set the preferred HSPA+ technology to DC-HSDPA+MIMO for a cell.

l (Optional) Select the DCMIMO_HSDPA check box under the HSPA TechnologiesRetried by UEs parameter to enable periodic DRD for DC-HSDPA+MIMO.

NOTE

l Before enabling periodic DRD for DC-HSDPA+MIMO, enable periodic DRD for other features onwhich this feature depends. That is, select the DC_HSDPA and MIMO check boxes under the HSPATechnologies Retried by UEs parameter.

l Before verifying this feature, perform the operations described in step 2. If the preferred HSPA+technology planned for a cell is not DC-HSDPA+MIMO, modify the configuration based on thenetwork plan after feature verification.

Step 3 To enable the switch for cell-level DC-HSDPA+MIMO, run the RNC MML command MODUCELLALGOSWITCH (CME single configuration: UMTS Cell Configuration Express >Cell Parameters > Cell Algorithm Switches; CME batch modification center: ModifyingUMTS Cell Parameters in Batches). In this step, select the DCMIMO_HSDPA check box underthe Cell Hspa Plus function switch parameter.

NOTE

The switch for cell-level DC-HSDPA+MIMO must be turned on for both cells in the DC-HSDPA group.

Step 4 Enable DC-HSDPA+MIMO for the local cell on the NodeB side as follows:l For NodeBs running the V200R015, run the MML command ADD/MOD ULOCELL (CME

single configuration: NodeB Configuration Express > IUB_NodeB > Radio Layer > xxSector > Locell; CME batch modification center: Modifying Physical NodeB Parameters inBatches) with DC-HSDPA+MIMO set to TRUE(TRUE) on the NodeB.

l For NodeBs running the V100R015, run the MML command ADD LOCELL or MODLOCELL.

----End

7.2.4.4.2 MML Command Examples/*Activating DC-HSDPA+MIMO*///Enabling the algorithm switch for RNC-level DC-HSDPA+MIMO SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_MIMO_SWITCH-1&CFG_HSDPA_DCMIMO_SWITCH-1; //(Optional) Enabling the algorithm switch for streaming services over HSDPA if HSDPA is required for streaming services SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-1; //Enabling the retried switch for DC-HSDPA+MIMO SET UFRC: RetryCapability=DCMIMO_HSDPA-1; //Setting HSDPA thresholds for downlink streaming services and for downlink BE services SET UFRCCHLTYPEPARA: DlStrThsOnHsdpa=D64, DlBeTraffThsOnHsdpa=D64; //Enabling the switch for cell-level DC-HSDPA+MIMO and the algorithm switch for DL Layer2 Improvement on the RNC side MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DCMIMO_HSDPA-1;



55

//Enabling the algorithm switch for DC-HSDPA+MIMO on the NodeB side //V200R015 NodeB MOD ULOCELL: ULOCELLID=1; HSDPADCMIMO=TRUE; //V100R015 NodeB MOD LOCELL: LOCELL=1, DC_MIMO=TRUE;

7.2.4.5 Activation Observation

Step 1 Check the number of online DC-HSDPA+MIMO users. The VS.HSDPA.UE.Mean.CAT25.28counter measures the average number of HSDPA users in HS-DSCH categories 25 to 28 in acell. The VS.HSDPA.UE.Max.CAT25.28 counter measures the maximum number of HSDPAusers in HS-DSCH categories 25 to 28 in a cell.

Step 2 Check the number of DC-HSDPA+MIMO RAB setups. TheVS.HSDPA.RAB.DCMIMO.AttEstab counter measures the number of DC-HSDPA+MIMORAB setup attempts on the primary carrier in a DC-HSDPA+MIMO cell group. TheVS.HSDPA.RAB.DCMIMO.SuccEstab counter measures the number of successful DC-HSDPA+MIMO RAB setups on the primary carrier in a DC-HSDPA+MIMO cell group.

Step 3 Check the number of DC-HSDPA+MIMO call drops. TheVS.HSDPA.RAB.DCMIMO.NormRel counter measures the number of DC-HSDPA+MIMORABs that are normally released on the primary carrier in a DC-HSDPA+MIMO cell group.The VS.HSDPA.RAB.DCMIMO.AbnormRel counter measures the number of DC-HSDPA+MIMO RABs that are abnormally released on the primary carrier in a DC-HSDPA+MIMOcell group (including RF failures).

Step 4 Start a UE trace task and use the UE to establish HSPA best effort (BE) services. Check whetherthe RADIO BEARER SETUP message over the Uu interface contains the "dl-SecondaryCellInfoFDD" and "secondaryCellMIMOparameters" IEs.

l If the message contains both IEs, as shown in Figure 7-3, this feature has been activated.

l If the message contains only one of the preceding IEs, this feature has not been activated.

Figure 7-3 RADIO BEARER SETUP message

----End

7.2.4.6 Deactivation



56


Step 1 Run the RNC MML command SET UCORRMALGOSWITCH (CME single configuration:UMTS Radio Global Configuration Express > Connection_Oriented RRM SwitchConfiguration > Connection Oriented Algorithm Switches; CME batch modification center:Modifying RNC Parameters in Batches). In this step, deselectCFG_HSDPA_DCMIMO_SWITCH and CFG_HSDPA_MIMO_SWITCH check boxesunder the Channel Configuration Strategy Switch parameter to disable the algorithm switchfor RNC-level DC-HSDPA+MIMO on the RNC.

Step 2 Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration:UMTS Cell Configuration Express > Cell Parameters > Cell Algorithm Switches; CMEbatch modification center: Modifying UMTS Cell Parameters in Batches). In this step, deselectthe DCMIMO_HSDPA(Cell DC-HSDPA Combined with MIMO Function Switch) checkbox under the Cell Hspa Plus function switch parameter to disable the algorithm switch forcell-level DC-HSDPA+MIMO on the RNC.

Step 3 Disable DC-HSDPA+MIMO for the local cell on the NodeB side as follows:

l For NodeBs running V200R015, run the MML command MOD ULOCELL (CME singleconfiguration: NodeB Configuration Express > IUB_NodeB > Radio Layer > xx Sector> Locell; CME batch modification center: Modifying Physical NodeB Parameters inBatches). In this step, set DC-HSDPA+MIMO to FALSE(FALSE) to disable the algorithmswitch for DC-HSDPA+MIMO on the NodeB.

l For NodeBs running V100R015, run the MML command MOD LOCELL.

----End

7.2.4.6.2 MML Command Examples /*Deactivating DC-HSDPA+MIMO*/ //Disabling the algorithm switch for RNC-level DC-HSDPA+MIMO SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_MIMO_SWITCH-0&CFG_HSDPA_DCMIMO_SWITCH-0; //Disabling the switch for cell-level DC-HSDPA+MIMO on the RNC side MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DCMIMO_HSDPA-0; //Disabling the switch for DC-HSDPA+MIMO on the NodeB side //V200R015 NodeB MOD ULOCELL: ULOCELLID=1; HSDPADCMIMO=FALSE; //V100R015 NodeB MOD LOCELL: LOCELL=1, DC_MIMO=FALSE;

7.2.5 Performance MonitoringTo determine the number of DC-HSDPA+MIMO RABs or UEs in a cell, view the followingRNC counters:

l VS.HSDPA.RAB.DCMIMO.AttEstab: Number of DC-HSDPA+MIMO RAB SetupRequests in the Primary Carrier of DC-HSDPA for Cell

l VS.HSDPA.RAB.DCMIMO.SuccEstab: Number of Successful DC-HSDPA+MIMORAB Setups in the Primary Carrier of DC-HSDPA for cell

l VS.HSDPA.RAB.DCMIMO.NormRel: Number of Normal DC-HSDPA+MIMO RABReleases in the Primary Carrier of DC-HSDPA for cell

l VS.HSDPA.RAB.DCMIMO.AbnormRel: Number of Abnormal DC-HSDPA+MIMORAB Releases in the Primary Carrier of DC-HSDPA for cell



57

DC-HSDPA+MIMO increases the single-user peak rate and cell throughput. To determine theaverage HSDPA throughput and total downlink throughput before and after DC-HSDPA+MIMO is activated, view the following counters:

l VS.HSDPA.MeanChThroughput: an RNC counter that measures the average downlinkthroughput of individual MAC-d flows for HSDPA in the cell.This counter measures the average throughput of HSDPA services in the cell. The single-user peak rate needs to be checked through drive tests.

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

The values of the preceding counters increase after this feature is activated.

The performance gain provided by DC-HSDPA+MIMO is related to the number of UEssupporting DC-HSDPA+MIMO and the number of UEs that do not support DC-HSDPA+MIMOin a cell. Generally, the larger the proportion of UEs supporting DC-HSDPA+MIMO, the greaterthe performance gain is. When the UEs in a cell all support DC-HSDPA+MIMO, theperformance gains reach the maximum.

7.2.6 Parameter OptimizationNone

7.2.7 TroubleshootingTable 7-8 lists the alarms related to DC-HSDPA+MIMO.

Table 7-8 Alarms related to DC-HSDPA+MIMO

AlarmID

Alarm Name NE Feature ID Feature Name

22221 UMTS Cell DC-HSDPA Function Fault

RNC WRFD-010699 DC-HSDPA+MIMO

28206 Local Cell CapabilityDecline

NodeB WRFD-010699 DC-HSDPA+MIMO



58

8 Parameters

Table 8-1 Parameter description

Parameter ID NE MMLCommand

Feature ID Feature Name Description

TCell BSC6900 ADDUCELLSETUPMODUCELLSETUP

WRFD-010699WRFD-022000WRFD-150207WRFD-150209WRFD-150208WRFD-150250WRFD-150223WRFD-010696WRFD-150227WRFD-021309WRFD-021308

DC-HSDPA+MIMOPhysicalChannelManagement4C-HSDPADB-HSDPAFlexible DualCarrier HSDPA3C-HSDPAMC-HSDPA+MIMODC-HSDPADB-HSDPA+MIMOImprovedDownlinkCoverageExtended CellCoverage up to200km

Meaning:Differ-ence betweenthe SystemFrame Number(SFN) andNodeB FrameNumber (BFN)of the NodeBwhich the cellbelongs to. It isrecommendedthat TCell of allintra-frequencyneighboringcells under oneNodeB shouldbe unique. TCellof DC carriergroup cells orMC carriergroup cells mustbe the same. Fordetailedinformation ofthis parameter,see 3GPP TS25.402.GUI ValueRange:CHIP0,CHIP256,CHIP512,

WCDMA RANDC-HSDPA Feature Parameter Description 8 Parameters


59



CHIP768,CHIP1024,CHIP1280,CHIP1536,CHIP1792,CHIP2048,CHIP2304Unit:chipActual ValueRange:CHIP0,CHIP256,CHIP512,CHIP768,CHIP1024,CHIP1280,CHIP1536,CHIP1792,CHIP2048,CHIP2304DefaultValue:None



60



TCell BSC6910 ADDUCELLSETUPMODUCELLSETUP

WRFD-010699WRFD-022000WRFD-150207WRFD-150209WRFD-150208WRFD-150250WRFD-150223WRFD-010696WRFD-150227WRFD-021309WRFD-021308

DC-HSDPA+MIMOPhysicalChannelManagement4C-HSDPADB-HSDPAFlexible DualCarrier HSDPA3C-HSDPAMC-HSDPA+MIMODC-HSDPADB-HSDPA+MIMOImprovedDownlinkCoverageExtended CellCoverage up to200km

Meaning:Differ-ence betweenthe SystemFrame Number(SFN) andNodeB FrameNumber (BFN)of the NodeBwhich the cellbelongs to. It isrecommendedthat TCell of allintra-frequencyneighboringcells under oneNodeB shouldbe unique. TCellof DC carriergroup cells orMC carriergroup cells mustbe the same. Fordetailedinformation ofthis parameter,see 3GPP TS25.402.GUI ValueRange:CHIP0,CHIP256,CHIP512,CHIP768,CHIP1024,CHIP1280,CHIP1536,CHIP1792,CHIP2048,CHIP2304Unit:chipActual ValueRange:CHIP0,CHIP256,CHIP512,CHIP768,CHIP1024,CHIP1280,CHIP1536,



61



CHIP1792,CHIP2048,CHIP2304DefaultValue:None



62



UARFCNDownlink

BSC6900 ADDUCELLSETUPMODUCELLFREQUENCYMODUCELLSETUP

WRFD-010101 3GPP R9Specifications

Meaning:Depending on the valueof [Bandindication], asshown below:Band1 Generalfrequencies:[10562-10838]Additionalfrequencies:none Band2Generalfrequencies:[9662-9938]Additionalfrequencies:{412,437,462,487,512,537,562,587,612,637,662,687} Band3Generalfrequencies:[1162-1513]Additionalfrequencies:none Band4Generalfrequencies:[1537-1738]Additionalfrequencies:{1887, 1912,1937, 1962,1987, 2012,2037, 2062,2087} Band5Generalfrequencies:[4357-4458]Additionalfrequencies:{1007, 1012,1032,1037,1062, 1087}Band6 Generalfrequencies:[4387-4413]Additional



63



frequencies:{1037, 1062}Band7 Generalfrequencies:[2237-2563]Additionalfrequencies:{2587, 2612,2637, 2662,2687, 2712,2737, 2762,2787, 2812,2837, 2862,2887, 2912}Band8 Generalfrequencies:[2937-3088]Additionalfrequencies:none Band9Generalfrequencies:[9237-9387]Additionalfrequencies:noneBandIndNotUsed:[0-16383]DownlinkUARFCN of acell.For detailedinformation ofthis parameter,see 3GPP TS25.433.GUI ValueRange:0~16383Unit:NoneActual ValueRange:0~16383DefaultValue:None



64



UARFCNDownlink



Meaning:Depending on the valueof [Bandindication], asshown below:Band1 Generalfrequencies:[10562-10838]Additionalfrequencies:none Band2Generalfrequencies:[9662-9938]Additionalfrequencies:{412,437,462,487,512,537,562,587,612,637,662,687} Band3Generalfrequencies:[1162-1513]Additionalfrequencies:none Band4Generalfrequencies:[1537-1738]Additionalfrequencies:{1887, 1912,1937, 1962,1987, 2012,2037, 2062,2087} Band5Generalfrequencies:[4357-4458]Additionalfrequencies:{1007, 1012,1032,1037,1062, 1087}Band6 Generalfrequencies:[4387-4413]Additional



65



frequencies:{1037, 1062}Band7 Generalfrequencies:[2237-2563]Additionalfrequencies:{2587, 2612,2637, 2662,2687, 2712,2737, 2762,2787, 2812,2837, 2862,2887, 2912}Band8 Generalfrequencies:[2937-3088]Additionalfrequencies:none Band9Generalfrequencies:[9237-9387]Additionalfrequencies:noneBandIndNotUsed:[0-16383]DownlinkUARFCN of acell.For detailedinformation ofthis parameter,see 3GPP TS25.433.GUI ValueRange:0~16383Unit:NoneActual ValueRange:0~16383DefaultValue:None



66



UARFCNUplink



Meaning:Depending on the valueof [Bandindication], asshown below:Band1: Generalfrequencies:[9612-9888]Additionalfrequencies:none Band2:Generalfrequencies:[9262-9538]Additionalfrequencies:{12,37,62,87,112,137,162,187,212,237,262,287} Band3:Generalfrequencies:[937-1288]Additionalfrequencies:none Band4:Generalfrequencies:[1312-1513]Additionalfrequencies:{1662, 1687,1712, 1737,1762, 1787,1812, 1837,1862} Band5:Generalfrequencies:[4132-4233]Additionalfrequencies:{782, 787, 807,812, 837, 862}Band6: Generalfrequencies:[4162-4188]Additionalfrequencies:



67



{812, 837}Band7: Generalfrequencies:[2012-2338]Additionalfrequencies:{2362, 2387,2412, 2437,2462, 2487,2512, 2537,2562, 2587,2612, 2637,2662, 2687}Band8: Generalfrequencies:[2712-2863]Additionalfrequencies:none Band9:Generalfrequencies:[8762-8912]Additionalfrequencies:noneBandIndNotUsed: [0-16383]UplinkUARFCN of acell. Suppose theUplinkUARFCN isunspecified andthe value of[Bandindication] isBand1, Band2,Band3, Band4,Band5, Band6,Band7,Band8,orBand9. Then thedefault UplinkUARFCN is asfollows: If theDL frequencybelongs tocommon



68



frequencies,then Band1:UplinkUARFCN =DownlinkUARFCN - 950Band2: UplinkUARFCN =DownlinkUARFCN - 400Band3: UplinkUARFCN =DownlinkUARFCN - 225Band4: UplinkUARFCN =DownlinkUARFCN - 225Band5: UplinkUARFCN =DownlinkUARFCN - 225Band6: UplinkUARFCN =DownlinkUARFCN - 225Band7: UplinkUARFCN =DownlinkUARFCN - 225Band8: UplinkUARFCN =DownlinkUARFCN - 225Band9: UplinkUARFCN =DownlinkUARFCN - 475If the DLfrequencybelongs tospecialfrequencies,then Band2:UplinkUARFCN =DownlinkUARFCN - 400



69



Band4: UplinkUARFCN =DownlinkUARFCN - 225Band5: UplinkUARFCN =DownlinkUARFCN - 225Band6: UplinkUARFCN =DownlinkUARFCN - 225Band7: UplinkUARFCN =DownlinkUARFCN - 225For detailedinformation ofthis parameter,see 3GPP TS25.433.GUI ValueRange:0~16383Unit:NoneActual ValueRange:0~16383DefaultValue:None



70



UARFCNUplink



Meaning:Depending on the valueof [Bandindication], asshown below:Band1: Generalfrequencies:[9612-9888]Additionalfrequencies:none Band2:Generalfrequencies:[9262-9538]Additionalfrequencies:{12,37,62,87,112,137,162,187,212,237,262,287} Band3:Generalfrequencies:[937-1288]Additionalfrequencies:none Band4:Generalfrequencies:[1312-1513]Additionalfrequencies:{1662, 1687,1712, 1737,1762, 1787,1812, 1837,1862} Band5:Generalfrequencies:[4132-4233]Additionalfrequencies:{782, 787, 807,812, 837, 862}Band6: Generalfrequencies:[4162-4188]Additionalfrequencies:



71



{812, 837}Band7: Generalfrequencies:[2012-2338]Additionalfrequencies:{2362, 2387,2412, 2437,2462, 2487,2512, 2537,2562, 2587,2612, 2637,2662, 2687}Band8: Generalfrequencies:[2712-2863]Additionalfrequencies:none Band9:Generalfrequencies:[8762-8912]Additionalfrequencies:noneBandIndNotUsed: [0-16383]UplinkUARFCN of acell. Suppose theUplinkUARFCN isunspecified andthe value of[Bandindication] isBand1, Band2,Band3, Band4,Band5, Band6,Band7,Band8,orBand9. Then thedefault UplinkUARFCN is asfollows: If theDL frequencybelongs tocommon



72



frequencies,then Band1:UplinkUARFCN =DownlinkUARFCN - 950Band2: UplinkUARFCN =DownlinkUARFCN - 400Band3: UplinkUARFCN =DownlinkUARFCN - 225Band4: UplinkUARFCN =DownlinkUARFCN - 225Band5: UplinkUARFCN =DownlinkUARFCN - 225Band6: UplinkUARFCN =DownlinkUARFCN - 225Band7: UplinkUARFCN =DownlinkUARFCN - 225Band8: UplinkUARFCN =DownlinkUARFCN - 225Band9: UplinkUARFCN =DownlinkUARFCN - 475If the DLfrequencybelongs tospecialfrequencies,then Band2:UplinkUARFCN =DownlinkUARFCN - 400



73



Band4: UplinkUARFCN =DownlinkUARFCN - 225Band5: UplinkUARFCN =DownlinkUARFCN - 225Band6: UplinkUARFCN =DownlinkUARFCN - 225Band7: UplinkUARFCN =DownlinkUARFCN - 225For detailedinformation ofthis parameter,see 3GPP TS25.433.GUI ValueRange:0~16383Unit:NoneActual ValueRange:0~16383DefaultValue:None



74



CfgSwitch BSC6900 SETUCORRMALGOSWITCH

WRFD-010699WRFD-010693WRFD-010694WRFD-010697WRFD-010696WRFD-150250WRFD-010101WRFD-010510WRFD-011500WRFD-010686WRFD-010687WRFD-010684WRFD-010683WRFD-01061502WRFD-01061503WRFD-01061501WRFD-01061504WRFD-150207WRFD-150227WRFD-02060504WRFD-150223WRFD-150209WRFD-010615WRFD-010617WRFD-020134

DC-HSDPA+MIMO

DL 64QAM+MIMO

UL 16QAM

E-DPCCHBoosting

DC-HSDPA

3C-HSDPA

3GPP R9Specifications

3.4/6.8/13.6/27.2Kbps RRCConnection andRadio AccessBearerEstablishmentand Release

PDCP HeaderCompression(RFC2507)

CPC - DTX /DRX

CPC - HS-SCCH lessoperation

2x2 MIMO

Downlink64QAM

Combination ofOne CS Serviceand Two PSServices

Combination ofThree PSServices

Combination ofTwo PSServices

Combination ofOne CS Serviceand Three PSServices

Meaning:Channel configurationstrategy switchgroup. 1.CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH: When thisswitch is turnedon, the RNCdetermineswhether toenable the DC-HSDPA orMIMO featurefor a newlyadmitted userbased on the cellload and thenumber ofHSDPA users.2.CFG_DL_BLIND_DETECTION_SWITCH:When the switchis on, the DLblind transportformat detectionfunction is usedfor single SRBand AMR+SRBbearers. Notethat the UE isonly required tosupport the blindtransport formatstipulated in3GPP 25.212section 4.3.1. 3.CFG_EDPCCH_BOOSTING_SWITCH: Whenthe switch is on,Boosting can beconfigured forthe HSUPAservice. 4.



75



4C-HSDPADB-HSDPA+MIMOLossless SRNSRelocationMC-HSDPA+MIMODB-HSDPAMultiple RABPackage(PSRAB >= 2)VoIP overHSPA/HSPA+Push to Talk

CFG_FREE_USER_SWITCH:When thisswitch is turnedon, specialhandling for freeaccess user isenabled. 5.CFG_HSDPA_64QAM_SWITCH: When theswitch is on,64QAM can beconfigured forthe HSDPAservice. 6.CFG_HSDPA_DCMIMO_SWITCH: When thisswitch is turnedon, DC+MIMOcan beconfigured forthe HSDPAservice. 7.CFG_HSDPA_DC_SWITCH:When the switchis on, DC can beconfigured forthe HSDPAservice. 8.CFG_HSDPA_MIMO_SWITCH: When theswitch is on,MIMO can beconfigured forthe HSDPAservice. 9.CFG_HSDPA_MIMO_WITH_64QAM_SWITCH: When theswitch is on andthe switches for64QAM andMIMO are on,



76



64QAM+MIMO can beconfigured forthe HSDPAservice 10.CFG_HSDPA_4C_MIMO_SWITCH: Whetherthe 4C-HSDPA+MIMO featureis allowed forHSDPAservices. Whenthis switch isturned on, theMC-HSDPA+MIMO (4C-HSDPA+MIMO and3C-HSDPA+MIMO)feature isallowed forHSDPAservices. 11.CFG_HSDPA_4C_SWITCH:Whether the 3C-HSDPA or 4C-HSDPA featureis allowed forHSDPAservices. Whenthis switch isturned on, the3C-HSDPA or4C-HSDPAfeature isallowed forHSDPAservices. 12.CFG_HSDPA_DBMIMO_SWITCH: Whetherthe DB-HSDPA+MIMO featureis allowed forHSDPA



77



services. Whenthis switch isturned on, theDB-HSDPA+MIMO featureis allowed forHSDPAservices. 13.CFG_HSDPA_DB_SWITCH:Whether theDB-HSDPAfeature isallowed forHSDPAservices. Whenthis switch isturned on, theDB-HSDPAfeature isallowed forHSDPAservices. 14.CFG_HSPA_DTX_DRX_SWITCH: When theswitch is on,DTX_DRX canbe configuredfor the HSPAservice. 15.CFG_HSPA_HSSCCH_LESS_OP_SWITCH:When the switchis on, HS-SCCHLess Operationcan beconfigured forthe HSPAservice. 16.CFG_HSUPA_16QAM_SWITCH: When theswitch is on,16QAM can beconfigured forthe HSUPA



78



service. 17.CFG_HSUPA_DC_SWITCH:When thisswitch is turnedon, the DC-HSUPAfunction can beenabled forHSUPAservices. 18.CFG_IMS_SUPPORT_SWITCH: When theswitch is on andthe IMS licenseis activated, theRNC supportsIMS signaling.19.CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITCH:Whether theUTRANsupports thefunction oflossless RLCPDU sizechange. Whenthis switch isturned on,downlinkchannelreconfigurationbetween theDCH and HS-DSCH does notcause RLC PDUsize changewhich results inpacket loss. Thisfunction takeseffect only onthe UEs enabledwith thisfunction. For



79



details about thisfunction, see3GPP TS25.331. 20.CFG_LOSSLESS_RELOC_CFG_SWITCH:When the switchis on and the UEsupports losslessrelocation, theRNC configureslosslessrelocation forPDCPparameters if therequirements ofRLC mode,discard mode,and sequentialsubmission aremet. Then,losslessrelocation isused for the UE.21.CFG_MULTI_RAB_SWITCH: When theswitch is on, theRNC supportsmulti-RABscombinationssuch as 2CS,2CS+1PS, 1CS+2PS, and 2PS.22.CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH: When theswitch is on andthe PDCPHeadercompressionlicense isactivated, thePDCP header



80



compressionalgorithm forIPv6 is used atthe RNC. 23.CFG_PDCP_RFC2507_HC_SWITCH: Whenthe switch is onand the PDCPHeadercompressionlicense isactivated, thePDCP RFC2507headercompressionalgorithm isused for theRNC. 24.CFG_PDCP_RFC3095_HC_SWITCH: Whenthe switch is onand the PDCPROHC license isactivated, thePDCP RFC3095headercompressionalgorithm isused for theRNC. 25.CFG_PTT_SWITCH: When thisswitch is on, theRNC identifiesthe PTT userbased on theQoS attributes inthe RABassignmentrequestmessage. Then,the PTT usersare subject tospecialprocessing. 26.CFG_RAB_RE



81



L_RMV_HSPAPLUS_SWITCH: When thisswitch is on andif an RABrelease isperformed, theRNC decideswhether to fallback a certainHSPA(HSPA+)feature based onthe requirementof remainingtraffic carried bythe UE. That is,if an HSPA+feature isrequired by thepreviouslyreleased RABconnection butis not required inthe initial bearerpolicy of theremainingtraffic, the RNCfalls back thefeature to savethe transmissionresources. TheHSPA+ featuresthat support thefallback areMIMO,64QAM, MIMO+64QAM, UL16QAM, DC-HSDPA, ULTTI 2ms, andDC-HSUPA.27.CFG_RCS_E_SWITCH:Indicateswhether toenable the RCS-e (Rich



82



CommunicationSuit enhanced)service thatsupports voiceservices carriedin the CSdomain andvideo servicescarried in the PSdomain. Whenthis switch isturned off, theRCS-e service isdisabled. Whenthis switch isturned on, theRCS-e service isenabled. 28.CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWITCH:Switch for AMRLCretransmissionparameters forUEs in theCELL_FACHstate.When thisswitch is turnedon, the"TimerPoll" and"NoDiscardMaxDAT"parameters inthe "SETUFACHCFGPARA" commandare used for theAM RLCretransmissionparametersspecific to PSservices andSRBs.When thisswitch is turnedoff, the"TimerPoll" and



83



"NoDiscardMaxDAT"parameters inthe "ADDUTYPSRBRLC" command areused for the AMRLCretransmissionparametersspecific toSRBs. Inaddition, the"TimerPoll" and"NoDiscardMaxDAT" in the"ADDUTYPRABRLC" command areused for the AMRLCretransmissionparametersspecific to PSservices. 29.CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SWITCH:Switchcontrolling theconfigurationmode of AMRLC SDUretransmissionparameters forUEs in theCELL_DCHstate. When thisswitch is turnedon and UEs inthe CELL_DCHstate, on theRNC, thetransmitting sideof an AM RLCentity uses thevalues of the



84



"TimerPoll" and"NoDiscardMaxDAT"parameters inthe "ADDUTYPSRBDCHRNCRLC" or"MODUTYPSRBDCHRNCRLC"command forSDUretransmission.When thisswitch is turnedoff or UEs not inthe CELL_DCHstate, on theRNC, thetransmitting sideuses the valuesof theseparameters inthe "ADDUTYPSRBRLC" or "MODUTYPSRBRLC" command forSDUretransmission.GUI ValueRange:CFG_DL_BLIND_DETECTION_SWITCH,CFG_HSDPA_64QAM_SWITCH,CFG_HSDPA_MIMO_SWITCH,CFG_HSPA_DTX_DRX_SWITCH,CFG_HSPA_HSSCCH_LESS_OP_SWITCH,



85



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_HSDPA_MIMO_WITH_64QAM_SWITCH,CFG_HSDPA_DC_SWITCH,CFG_HSUPA_16QAM_SWITCH,CFG_RAB_REL_RMV_HSPAPLUS_SWITCH,CFG_PTT_SWITCH,CFG_EDPCCH_BOOSTING_SWITCH,CFG_HSDPA_DCMIMO_SWITCH,CFG_FREE_USER_SWITCH,CFG_DC_MIMO_DYNAMIC_



86



SELECT_SWITCH,CFG_HSUPA_DC_SWITCH,CFG_HSDPA_4C_MIMO_SWITCH,CFG_HSDPA_4C_SWITCH,CFG_HSDPA_DBMIMO_SWITCH,CFG_HSDPA_DB_SWITCH,CFG_RCS_E_SWITCH,CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWITCH,CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SWITCHUnit:NoneActual ValueRange:CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH,CFG_DL_BLIND_DETECTION_SWITCH,CFG_EDPCCH_BOOSTING_SWITCH,CFG_FREE_USER_SWITCH,CFG_HSDPA_64QAM_SWITCH,CFG_HSDPA_DCMIMO_SWITCH,CFG_HSDPA_DC_SWITCH,CFG_HSDPA_



87



MIMO_SWITCH,CFG_HSDPA_MIMO_WITH_64QAM_SWITCH,CFG_HSDPA_4C_MIMO_SWITCH,CFG_HSDPA_4C_SWITCH,CFG_HSDPA_DBMIMO_SWITCH,CFG_HSDPA_DB_SWITCH,CFG_HSPA_DTX_DRX_SWITCH,CFG_HSPA_HSSCCH_LESS_OP_SWITCH,CFG_HSUPA_16QAM_SWITCH,CFG_HSUPA_DC_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_R



88



FC3095_HC_SWITCH,CFG_PTT_SWITCH,CFG_RAB_REL_RMV_HSPAPLUS_SWITCH,CFG_RCS_E_SWITCH,CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWITCH,CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SWITCHDefaultValue:CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH:0,CFG_DL_BLIND_DETECTION_SWITCH:1,CFG_EDPCCH_BOOSTING_SWITCH:0,CFG_FREE_USER_SWITCH:0,CFG_HSDPA_64QAM_SWITCH:1,CFG_HSDPA_DCMIMO_SWITCH:0,CFG_HSDPA_DC_SWITCH:0,CFG_HSDPA_MIMO_SWITCH:1,CFG_HSDPA_MIMO_WITH_64QAM_SWITCH:



89



0,CFG_HSDPA_4C_MIMO_SWITCH:0,CFG_HSDPA_4C_SWITCH:0,CFG_HSDPA_DBMIMO_SWITCH:0,CFG_HSDPA_DB_SWITCH:0,CFG_HSPA_DTX_DRX_SWITCH:0,CFG_HSPA_HSSCCH_LESS_OP_SWITCH:0,CFG_HSUPA_16QAM_SWITCH:0,CFG_HSUPA_DC_SWITCH:0,CFG_IMS_SUPPORT_SWITCH:1,CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITCH:0,CFG_LOSSLESS_RELOC_CFG_SWITCH:0,CFG_MULTI_RAB_SWITCH:1,CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH:0,CFG_PDCP_RFC2507_HC_SWITCH:0,CFG_PDCP_RFC3095_HC_SWITCH:0,CFG_PTT_SWITCH:0,CFG_RAB_R



90



EL_RMV_HSPAPLUS_SWITCH:0,CFG_RCS_E_SWITCH:0,CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWITCH:0,CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SWITCH:0



91



CfgSwitch BSC6910 SETUCORRMALGOSWITCH

WRFD-010699WRFD-010693WRFD-010694WRFD-010697WRFD-010696WRFD-150250WRFD-010101WRFD-010510WRFD-011500WRFD-010686WRFD-010687WRFD-010684WRFD-010683WRFD-01061502WRFD-01061503WRFD-01061501WRFD-01061504WRFD-150207WRFD-150227WRFD-02060504WRFD-150223WRFD-150209WRFD-010615WRFD-010617WRFD-020134

DC-HSDPA+MIMO

DL 64QAM+MIMO

UL 16QAM

E-DPCCHBoosting

DC-HSDPA

3C-HSDPA

3GPP R9Specifications

3.4/6.8/13.6/27.2Kbps RRCConnection andRadio AccessBearerEstablishmentand Release

PDCP HeaderCompression(RFC2507)

CPC - DTX /DRX


2x2 MIMO

Downlink64QAM

Combination ofOne CS Serviceand Two PSServices

Combination ofThree PSServices


Combination ofOne CS Serviceand Three PSServices

Meaning:Channel configurationstrategy switchgroup. 1.CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH: When thisswitch is turnedon, the RNCdetermineswhether toenable the DC-HSDPA orMIMO featurefor a newlyadmitted userbased on the cellload and thenumber ofHSDPA users.2.CFG_DL_BLIND_DETECTION_SWITCH:When the switchis on, the DLblind transportformat detectionfunction is usedfor single SRBand AMR+SRBbearers. Notethat the UE isonly required tosupport the blindtransport formatstipulated in3GPP 25.212section 4.3.1. 3.CFG_EDPCCH_BOOSTING_SWITCH: Whenthe switch is on,Boosting can beconfigured forthe HSUPAservice. 4.



92



4C-HSDPADB-HSDPA+MIMOLossless SRNSRelocationMC-HSDPA+MIMODB-HSDPAMultiple RABPackage(PSRAB >= 2)VoIP overHSPA/HSPA+Push to Talk

CFG_FREE_USER_SWITCH:When thisswitch is turnedon, specialhandling for freeaccess user isenabled. 5.CFG_HSDPA_64QAM_SWITCH: When theswitch is on,64QAM can beconfigured forthe HSDPAservice. 6.CFG_HSDPA_DCMIMO_SWITCH: When thisswitch is turnedon, DC+MIMOcan beconfigured forthe HSDPAservice. 7.CFG_HSDPA_DC_SWITCH:When the switchis on, DC can beconfigured forthe HSDPAservice. 8.CFG_HSDPA_MIMO_SWITCH: When theswitch is on,MIMO can beconfigured forthe HSDPAservice. 9.CFG_HSDPA_MIMO_WITH_64QAM_SWITCH: When theswitch is on andthe switches for64QAM andMIMO are on,



93



64QAM+MIMO can beconfigured forthe HSDPAservice 10.CFG_HSDPA_4C_MIMO_SWITCH: Whetherthe 4C-HSDPA+MIMO featureis allowed forHSDPAservices. Whenthis switch isturned on, theMC-HSDPA+MIMO (4C-HSDPA+MIMO and3C-HSDPA+MIMO)feature isallowed forHSDPAservices. 11.CFG_HSDPA_4C_SWITCH:Whether the 3C-HSDPA or 4C-HSDPA featureis allowed forHSDPAservices. Whenthis switch isturned on, the3C-HSDPA or4C-HSDPAfeature isallowed forHSDPAservices. 12.CFG_HSDPA_DBMIMO_SWITCH: Whetherthe DB-HSDPA+MIMO featureis allowed forHSDPA



94



services. Whenthis switch isturned on, theDB-HSDPA+MIMO featureis allowed forHSDPAservices. 13.CFG_HSDPA_DB_SWITCH:Whether theDB-HSDPAfeature isallowed forHSDPAservices. Whenthis switch isturned on, theDB-HSDPAfeature isallowed forHSDPAservices. 14.CFG_HSPA_DTX_DRX_SWITCH: When theswitch is on,DTX_DRX canbe configuredfor the HSPAservice. 15.CFG_HSPA_HSSCCH_LESS_OP_SWITCH:When the switchis on, HS-SCCHLess Operationcan beconfigured forthe HSPAservice. 16.CFG_HSUPA_16QAM_SWITCH: When theswitch is on,16QAM can beconfigured forthe HSUPA



95



service. 17.CFG_HSUPA_DC_SWITCH:When thisswitch is turnedon, the DC-HSUPAfunction can beenabled forHSUPAservices. 18.CFG_IMS_SUPPORT_SWITCH: When theswitch is on andthe IMS licenseis activated, theRNC supportsIMS signaling.19.CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITCH:Whether theUTRANsupports thefunction oflossless RLCPDU sizechange. Whenthis switch isturned on,downlinkchannelreconfigurationbetween theDCH and HS-DSCH does notcause RLC PDUsize changewhich results inpacket loss. Thisfunction takeseffect only onthe UEs enabledwith thisfunction. For



96



details about thisfunction, see3GPP TS25.331. 20.CFG_LOSSLESS_RELOC_CFG_SWITCH:When the switchis on and the UEsupports losslessrelocation, theRNC configureslosslessrelocation forPDCPparameters if therequirements ofRLC mode,discard mode,and sequentialsubmission aremet. Then,losslessrelocation isused for the UE.21.CFG_MULTI_RAB_SWITCH: When theswitch is on, theRNC supportsmulti-RABscombinationssuch as 2CS,2CS+1PS, 1CS+2PS, and 2PS.22.CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH: When theswitch is on andthe PDCPHeadercompressionlicense isactivated, thePDCP header



97



compressionalgorithm forIPv6 is used atthe RNC. 23.CFG_PDCP_RFC2507_HC_SWITCH: Whenthe switch is onand the PDCPHeadercompressionlicense isactivated, thePDCP RFC2507headercompressionalgorithm isused for theRNC. 24.CFG_PDCP_RFC3095_HC_SWITCH: Whenthe switch is onand the PDCPROHC license isactivated, thePDCP RFC3095headercompressionalgorithm isused for theRNC. 25.CFG_PTT_SWITCH: When thisswitch is on, theRNC identifiesthe PTT userbased on theQoS attributes inthe RABassignmentrequestmessage. Then,the PTT usersare subject tospecialprocessing. 26.CFG_RAB_RE



98



L_RMV_HSPAPLUS_SWITCH: When thisswitch is on andif an RABrelease isperformed, theRNC decideswhether to fallback a certainHSPA(HSPA+)feature based onthe requirementof remainingtraffic carried bythe UE. That is,if an HSPA+feature isrequired by thepreviouslyreleased RABconnection butis not required inthe initial bearerpolicy of theremainingtraffic, the RNCfalls back thefeature to savethe transmissionresources. TheHSPA+ featuresthat support thefallback areMIMO,64QAM, MIMO+64QAM, UL16QAM, DC-HSDPA, ULTTI 2ms, andDC-HSUPA.27.CFG_RCS_E_SWITCH:Indicateswhether toenable the RCS-e (Rich



99



CommunicationSuit enhanced)service thatsupports voiceservices carriedin the CSdomain andvideo servicescarried in the PSdomain. Whenthis switch isturned off, theRCS-e service isdisabled. Whenthis switch isturned on, theRCS-e service isenabled. 28.CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWITCH:Switch for AMRLCretransmissionparameters forUEs in theCELL_FACHstate.When thisswitch is turnedon, the"TimerPoll" and"NoDiscardMaxDAT"parameters inthe "SETUFACHCFGPARA" commandare used for theAM RLCretransmissionparametersspecific to PSservices andSRBs.When thisswitch is turnedoff, the"TimerPoll" and



100



"NoDiscardMaxDAT"parameters inthe "ADDUTYPSRBRLC" command areused for the AMRLCretransmissionparametersspecific toSRBs. Inaddition, the"TimerPoll" and"NoDiscardMaxDAT" in the"ADDUTYPRABRLC" command areused for the AMRLCretransmissionparametersspecific to PSservices. 29.CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SWITCH:Switchcontrolling theconfigurationmode of AMRLC SDUretransmissionparameters forUEs in theCELL_DCHstate. When thisswitch is turnedon and UEs inthe CELL_DCHstate, on theRNC, thetransmitting sideof an AM RLCentity uses thevalues of the



101



"TimerPoll" and"NoDiscardMaxDAT"parameters inthe "ADDUTYPSRBDCHRNCRLC" or"MODUTYPSRBDCHRNCRLC"command forSDUretransmission.When thisswitch is turnedoff or UEs not inthe CELL_DCHstate, on theRNC, thetransmitting sideuses the valuesof theseparameters inthe "ADDUTYPSRBRLC" or "MODUTYPSRBRLC" command forSDUretransmission.GUI ValueRange:CFG_DL_BLIND_DETECTION_SWITCH,CFG_HSDPA_64QAM_SWITCH,CFG_HSDPA_MIMO_SWITCH,CFG_HSPA_DTX_DRX_SWITCH,CFG_HSPA_HSSCCH_LESS_OP_SWITCH,



102



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_HSDPA_MIMO_WITH_64QAM_SWITCH,CFG_HSDPA_DC_SWITCH,CFG_HSUPA_16QAM_SWITCH,CFG_RAB_REL_RMV_HSPAPLUS_SWITCH,CFG_PTT_SWITCH,CFG_EDPCCH_BOOSTING_SWITCH,CFG_HSDPA_DCMIMO_SWITCH,CFG_FREE_USER_SWITCH,CFG_DC_MIMO_DYNAMIC_



103



SELECT_SWITCH,CFG_HSUPA_DC_SWITCH,CFG_HSDPA_4C_MIMO_SWITCH,CFG_HSDPA_4C_SWITCH,CFG_HSDPA_DBMIMO_SWITCH,CFG_HSDPA_DB_SWITCH,CFG_RCS_E_SWITCH,CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWITCH,CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SWITCHUnit:NoneActual ValueRange:CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH,CFG_DL_BLIND_DETECTION_SWITCH,CFG_EDPCCH_BOOSTING_SWITCH,CFG_FREE_USER_SWITCH,CFG_HSDPA_64QAM_SWITCH,CFG_HSDPA_DCMIMO_SWITCH,CFG_HSDPA_DC_SWITCH,CFG_HSDPA_



104



MIMO_SWITCH,CFG_HSDPA_MIMO_WITH_64QAM_SWITCH,CFG_HSDPA_4C_MIMO_SWITCH,CFG_HSDPA_4C_SWITCH,CFG_HSDPA_DBMIMO_SWITCH,CFG_HSDPA_DB_SWITCH,CFG_HSPA_DTX_DRX_SWITCH,CFG_HSPA_HSSCCH_LESS_OP_SWITCH,CFG_HSUPA_16QAM_SWITCH,CFG_HSUPA_DC_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_R



105



FC3095_HC_SWITCH,CFG_PTT_SWITCH,CFG_RAB_REL_RMV_HSPAPLUS_SWITCH,CFG_RCS_E_SWITCH,CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWITCH,CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SWITCHDefaultValue:CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH:0,CFG_DL_BLIND_DETECTION_SWITCH:1,CFG_EDPCCH_BOOSTING_SWITCH:0,CFG_FREE_USER_SWITCH:0,CFG_HSDPA_64QAM_SWITCH:1,CFG_HSDPA_DCMIMO_SWITCH:0,CFG_HSDPA_DC_SWITCH:0,CFG_HSDPA_MIMO_SWITCH:1,CFG_HSDPA_MIMO_WITH_64QAM_SWITCH:



106



0,CFG_HSDPA_4C_MIMO_SWITCH:0,CFG_HSDPA_4C_SWITCH:0,CFG_HSDPA_DBMIMO_SWITCH:0,CFG_HSDPA_DB_SWITCH:0,CFG_HSPA_DTX_DRX_SWITCH:0,CFG_HSPA_HSSCCH_LESS_OP_SWITCH:0,CFG_HSUPA_16QAM_SWITCH:0,CFG_HSUPA_DC_SWITCH:0,CFG_IMS_SUPPORT_SWITCH:1,CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITCH:0,CFG_LOSSLESS_RELOC_CFG_SWITCH:0,CFG_MULTI_RAB_SWITCH:1,CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH:0,CFG_PDCP_RFC2507_HC_SWITCH:0,CFG_PDCP_RFC3095_HC_SWITCH:0,CFG_PTT_SWITCH:0,CFG_RAB_R



107



EL_RMV_HSPAPLUS_SWITCH:0,CFG_RCS_E_SWITCH:0,CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWITCH:0,CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SWITCH:0



108



HspaPlusSwitch BSC6900 ADDUCELLALGOSWITCHMODUCELLALGOSWITCH

WRFD-010699

WRFD-010401

WRFD-010504

WRFD-010693

WRFD-010695

WRFD-010694

WRFD-010697

WRFD-010696

WRFD-010501

WRFD-01061501

WRFD-150250

WRFD-01061008

WRFD-01061206

WRFD-140204

WRFD-01060901

WRFD-01060903

WRFD-01060902

WRFD-010702

WRFD-010701

WRFD-010609

WRFD-010510

WRFD-010688

WRFD-010686

WRFD-010687

WRFD-010684

WRFD-010685

WRFD-010683

WRFD-021000

WRFD-010503

WRFD-01061502

DC-HSDPA+MIMO

SystemInformationBroadcasting

BackgroundQoS Class

DL 64QAM+MIMO

UL Layer 2Improvement

UL 16QAM

E-DPCCHBoosting

DC-HSDPA

ConversationalQoS Class


3C-HSDPA

Interactive andBackgroundTraffic Class onHSDPA

Interactive andBackgroundTraffic Class onHSUPA

DC-HSUPA

Combination ofTwo CSServices(Except for TwoAMR SpeechServices)

Combination ofTwo CSServices andOne PS Service(Except for TwoAMR SpeechServices)

Meaning:Thisparameter isused to select afeature related toHSPA+. If afeature isselected, itindicates that thecorrespondingalgorithm isenabled. If afeature is notselected, itindicates that thecorrespondingalgorithm isdisabled. Notethat other factorssuch as licenseand the physicalcapability ofNodeB restrictwhether afeature can beused even if thisfeature isselected. TheEFACH/MIMOswitchdetermineswhether the cellsupports the E-FACH/MIMOfeature but doesnot affect theestablishment ofthe E-FACH andthe MIMO cell.1. 64QAM:When the switchis on, 64QAMcan beconfigured forthe HSDPAservice. 2.MIMO: Whenthe switch is on,MIMO can be



109



WRFD-01061503WRFD-010502WRFD-01061504WRFD-01061505WRFD-022000WRFD-150207WRFD-150227WRFD-150208WRFD-150223WRFD-020900WRFD-150209WRFD-010615WRFD-010632WRFD-010630

Combination ofOne CS Serviceand One PSServiceEnhanced DRXUplinkEnhancedCELL_FACHMultiple RABIntroductionPackage (PSRAB < 2)3.4/6.8/13.6/27.2Kbps RRCConnection andRadio AccessBearerEstablishmentand ReleaseDownlinkEnhancedCELL_FACHCPC - DTX /DRXCPC - HS-SCCH lessoperation2x2 MIMODownlinkEnhanced L2Downlink64QAMTransportChannelManagementInteractive QoSClassCombination ofOne CS Serviceand Two PSServicesCombination ofThree PSServices

configured forthe HSDPAservice.TheMIMO switchdetermineswhether the cellsupports theMIMO featurebut does notaffect theestablishment ofthe the MIMOcell. 3.E_FACH: Whenthe switch is on,E_FACH can beconfigured forthe HSDPAservice.TheE_FACH switchdetermineswhether the cellsupports theE_FACHfeature but doesnot affect theestablishment ofthe the MIMOcell. 4.DTX_DRX:When the switchis on,DTX_DRX canbe configuredfor the HSPAservice. 5.HS_SCCH_LESS_OPERATION: When theswitch is on, HS-SCCH LessOperation canbe configuredfor the HSPAservice. 6.DL_L2ENHANCED: When theswitch is on,



110



Streaming QoSClassCombination ofOne CS Serviceand Three PSServicesCombination ofFour PSServicesPhysicalChannelManagement4C-HSDPADB-HSDPA+MIMOFlexible DualCarrier HSDPAMC-HSDPA+MIMOLogical ChannelManagementDB-HSDPAMultiple RABPackage(PSRAB >= 2)StreamingTraffic Class onHSUPAStreamingTraffic Class onHSDPA

DL_L2ENHANCED can beconfigured forthe HSDPAservice. 7.64QAM_MIMO: When theswitch is on andthe switches for64QAM andMIMO are on,64QAM+MIMO can beconfigured forthe HSDPAservice 8.UL_16QAM:When the switchis on, 16QAMcan beconfigured forthe HSUPAservice. 9.DC_HSDPA:When the switchis on, DC can beconfigured forthe HSDPAservice. 10.UL_L2ENHANCED: When theswitch is on,UL_L2ENHANCED can beconfigured forthe HSUPAservice. 11.EDPCCH_BOOSTING: Whenthe switch is on,Boosting can beconfigured forthe HSUPAservice. 12.DCMIMO_HSDPA: When thisswitch is turnedon, DC+MIMO



111



can beconfigured forthe HSDPAservice. 13.E_DRX: Whenthe switch is on,E_DRX can beconfigured forthe HSUPAservice. 14.DC_HSUPA:When thisswitch is turnedon, the DC-HSUPAfunction can beenabled forHSUPAservices. 15.HSDPA_4C_MIMO: Whetherthe MC-HSDPA+MIMO featureis allowed forHSDPAservices. Whenthis switch isturned on, theMC-HSDPA+MIMO (3C-HSDPA+MIMO and4C-HSDPA+MIMO)feature isallowed forHSDPAservices. 16.HSDPA_4C:Whether the 3C-HSDPA or 4C-HSDPA featureis allowed forHSDPAservices. Whenthis switch isturned on, the3C-HSDPA or



112



4C-HSDPAfeature isallowed forHSDPAservices. 17.DBMIMO_HSDPA: Whetherthe DB-HSDPA+MIMO featureis allowed forHSDPAservices. Whenthis switch isturned on, theDB-HSDPA+MIMO featureis allowed forHSDPAservices. 18.DB_HSDPA:Whether theDB-HSDPAfeature isallowed forHSDPAservices. Whenthis switch isturned on, theDB-HSDPAfeature isallowed forHSDPAservices.GUI ValueRange:64QAM(Cell 64QAMFunctionSwitch), MIMO(Cell MIMOFunctionSwitch),E_FACH(CellE_FACHFunctionSwitch),DTX_DRX(Cell



113



DTX_DRXFunctionSwitch),HS_SCCH_LESS_OPERATION(CellHS_SCCHLESSOPERATIONFunctionSwitch),DL_L2ENHANCED(Cell DLL2ENHANCEDFunctionSwitch),64QAM_MIMO(Cell 64QAM+MIMOFunctionSwitch),UL_16QAM(Cell UL16QAMFunctionSwitch),DC_HSDPA(Cell DC-HSDPAFunctionSwitch),UL_L2ENHANCED(Cell ULL2ENHANCEDFunctionSwitch),EDPCCH_BOOSTING(Cell E-DPCCHBoostingFunctionSwitch),DCMIMO_HSDPA(Cell DC-HSDPACombined withMIMO FunctionSwitch),



114



E_DRX(EnhancedDiscontinuousReceptionFunctionSwitch),DC_HSUPA(Cell DC-HSUPAFunctionSwitch),HSDPA_4C_MIMO(4C-HSDPA+MIMOFunctionSwitch),HSDPA_4C(4C-HSDPAFunctionSwitch),DBMIMO_HSDPA(DB-HSDPA+MIMOFunctionSwitch),DB_HSDPA(DB-HSDPAFunctionSwitch)Unit:NoneActual ValueRange:64QAM,MIMO,E_FACH,DTX_DRX,HS_SCCH_LESS_OPERATION,DL_L2ENHANCED,64QAM_MIMO, UL_16QAM,DC_HSDPA,UL_L2ENHANCED,



115



EDPCCH_BOOSTING,DCMIMO_HSDPA, E_DRX,DC_HSUPA,HSDPA_4C_MIMO,HSDPA_4C,DBMIMO_HSDPA,DB_HSDPADefault Value:64QAM:0,MIMO:0,E_FACH:0,DTX_DRX:0,HS_SCCH_LESS_OPERATION:0,DL_L2ENHANCED:0,64QAM_MIMO:0,UL_16QAM:0,DC_HSDPA:0,UL_L2ENHANCED:0,EDPCCH_BOOSTING:0,DCMIMO_HSDPA:0,E_DRX:0,DC_HSUPA:0,HSDPA_4C_MIMO:0,HSDPA_4C:0,DBMIMO_HSDPA:0,DB_HSDPA:0



116



HspaPlusSwitch BSC6910 ADDUCELLALGOSWITCHMODUCELLALGOSWITCH

WRFD-010699

WRFD-010401

WRFD-010504

WRFD-010693

WRFD-010695

WRFD-010694

WRFD-010697

WRFD-010696

WRFD-010501

WRFD-01061501

WRFD-150250

WRFD-01061008

WRFD-01061206

WRFD-140204

WRFD-01060901

WRFD-01060903

WRFD-01060902

WRFD-010702

WRFD-010701

WRFD-010609

WRFD-010510

WRFD-010688

WRFD-010686

WRFD-010687

WRFD-010684

WRFD-010685

WRFD-010683

WRFD-021000

WRFD-010503

WRFD-01061502

DC-HSDPA+MIMO

SystemInformationBroadcasting

BackgroundQoS Class

DL 64QAM+MIMO

UL Layer 2Improvement

UL 16QAM

E-DPCCHBoosting

DC-HSDPA

ConversationalQoS Class


3C-HSDPA



DC-HSUPA

Combination ofTwo CSServices(Except for TwoAMR SpeechServices)

Combination ofTwo CSServices andOne PS Service(Except for TwoAMR SpeechServices)

Meaning:Thisparameter isused to select afeature related toHSPA+. If afeature isselected, itindicates that thecorrespondingalgorithm isenabled. If afeature is notselected, itindicates that thecorrespondingalgorithm isdisabled. Notethat other factorssuch as licenseand the physicalcapability ofNodeB restrictwhether afeature can beused even if thisfeature isselected. TheEFACH/MIMOswitchdetermineswhether the cellsupports the E-FACH/MIMOfeature but doesnot affect theestablishment ofthe E-FACH andthe MIMO cell.1. 64QAM:When the switchis on, 64QAMcan beconfigured forthe HSDPAservice. 2.MIMO: Whenthe switch is on,MIMO can be



117



WRFD-01061503WRFD-010502WRFD-01061504WRFD-01061505WRFD-022000WRFD-150207WRFD-150227WRFD-150208WRFD-150223WRFD-020900WRFD-150209WRFD-010615WRFD-010632WRFD-010630

Combination ofOne CS Serviceand One PSServiceEnhanced DRXUplinkEnhancedCELL_FACHMultiple RABIntroductionPackage (PSRAB < 2)3.4/6.8/13.6/27.2Kbps RRCConnection andRadio AccessBearerEstablishmentand ReleaseDownlinkEnhancedCELL_FACHCPC - DTX /DRXCPC - HS-SCCH lessoperation2x2 MIMODownlinkEnhanced L2Downlink64QAMTransportChannelManagementInteractive QoSClassCombination ofOne CS Serviceand Two PSServicesCombination ofThree PSServices

configured forthe HSDPAservice.TheMIMO switchdetermineswhether the cellsupports theMIMO featurebut does notaffect theestablishment ofthe the MIMOcell. 3.E_FACH: Whenthe switch is on,E_FACH can beconfigured forthe HSDPAservice.TheE_FACH switchdetermineswhether the cellsupports theE_FACHfeature but doesnot affect theestablishment ofthe the MIMOcell. 4.DTX_DRX:When the switchis on,DTX_DRX canbe configuredfor the HSPAservice. 5.HS_SCCH_LESS_OPERATION: When theswitch is on, HS-SCCH LessOperation canbe configuredfor the HSPAservice. 6.DL_L2ENHANCED: When theswitch is on,



118



Streaming QoSClassCombination ofOne CS Serviceand Three PSServicesCombination ofFour PSServicesPhysicalChannelManagement4C-HSDPADB-HSDPA+MIMOFlexible DualCarrier HSDPAMC-HSDPA+MIMOLogical ChannelManagementDB-HSDPAMultiple RABPackage(PSRAB >= 2)StreamingTraffic Class onHSUPAStreamingTraffic Class onHSDPA

DL_L2ENHANCED can beconfigured forthe HSDPAservice. 7.64QAM_MIMO: When theswitch is on andthe switches for64QAM andMIMO are on,64QAM+MIMO can beconfigured forthe HSDPAservice 8.UL_16QAM:When the switchis on, 16QAMcan beconfigured forthe HSUPAservice. 9.DC_HSDPA:When the switchis on, DC can beconfigured forthe HSDPAservice. 10.UL_L2ENHANCED: When theswitch is on,UL_L2ENHANCED can beconfigured forthe HSUPAservice. 11.EDPCCH_BOOSTING: Whenthe switch is on,Boosting can beconfigured forthe HSUPAservice. 12.DCMIMO_HSDPA: When thisswitch is turnedon, DC+MIMO



119



can beconfigured forthe HSDPAservice. 13.E_DRX: Whenthe switch is on,E_DRX can beconfigured forthe HSUPAservice. 14.DC_HSUPA:When thisswitch is turnedon, the DC-HSUPAfunction can beenabled forHSUPAservices. 15.HSDPA_4C_MIMO: Whetherthe MC-HSDPA+MIMO featureis allowed forHSDPAservices. Whenthis switch isturned on, theMC-HSDPA+MIMO (3C-HSDPA+MIMO and4C-HSDPA+MIMO)feature isallowed forHSDPAservices. 16.HSDPA_4C:Whether the 3C-HSDPA or 4C-HSDPA featureis allowed forHSDPAservices. Whenthis switch isturned on, the3C-HSDPA or



120



4C-HSDPAfeature isallowed forHSDPAservices. 17.DBMIMO_HSDPA: Whetherthe DB-HSDPA+MIMO featureis allowed forHSDPAservices. Whenthis switch isturned on, theDB-HSDPA+MIMO featureis allowed forHSDPAservices. 18.DB_HSDPA:Whether theDB-HSDPAfeature isallowed forHSDPAservices. Whenthis switch isturned on, theDB-HSDPAfeature isallowed forHSDPAservices.GUI ValueRange:64QAM(Cell 64QAMFunctionSwitch), MIMO(Cell MIMOFunctionSwitch),E_FACH(CellE_FACHFunctionSwitch),DTX_DRX(Cell



121



DTX_DRXFunctionSwitch),HS_SCCH_LESS_OPERATION(CellHS_SCCHLESSOPERATIONFunctionSwitch),DL_L2ENHANCED(Cell DLL2ENHANCEDFunctionSwitch),64QAM_MIMO(Cell 64QAM+MIMOFunctionSwitch),UL_16QAM(Cell UL16QAMFunctionSwitch),DC_HSDPA(Cell DC-HSDPAFunctionSwitch),UL_L2ENHANCED(Cell ULL2ENHANCEDFunctionSwitch),EDPCCH_BOOSTING(Cell E-DPCCHBoostingFunctionSwitch),DCMIMO_HSDPA(Cell DC-HSDPACombined withMIMO FunctionSwitch),



122



E_DRX(EnhancedDiscontinuousReceptionFunctionSwitch),DC_HSUPA(Cell DC-HSUPAFunctionSwitch),HSDPA_4C_MIMO(4C-HSDPA+MIMOFunctionSwitch),HSDPA_4C(4C-HSDPAFunctionSwitch),DBMIMO_HSDPA(DB-HSDPA+MIMOFunctionSwitch),DB_HSDPA(DB-HSDPAFunctionSwitch)Unit:NoneActual ValueRange:64QAM,MIMO,E_FACH,DTX_DRX,HS_SCCH_LESS_OPERATION,DL_L2ENHANCED,64QAM_MIMO, UL_16QAM,DC_HSDPA,UL_L2ENHANCED,



123



EDPCCH_BOOSTING,DCMIMO_HSDPA, E_DRX,DC_HSUPA,HSDPA_4C_MIMO,HSDPA_4C,DBMIMO_HSDPA,DB_HSDPADefault Value:64QAM:0,MIMO:0,E_FACH:0,DTX_DRX:0,HS_SCCH_LESS_OPERATION:0,DL_L2ENHANCED:0,64QAM_MIMO:0,UL_16QAM:0,DC_HSDPA:0,UL_L2ENHANCED:0,EDPCCH_BOOSTING:0,DCMIMO_HSDPA:0,E_DRX:0,DC_HSUPA:0,HSDPA_4C_MIMO:0,HSDPA_4C:0,DBMIMO_HSDPA:0,DB_HSDPA:0



124



MIMO64QA-MorDCHSDPASwitch

BSC6900 SET UFRC WRFD-020400WRFD-010696

DRDIntroductionPackageDC-HSDPA

Meaning:Thisswitch is used toconfigure thepriority ofMIMO_64QAM or DC-HSDPA.According todifferentprotocols, thefollowingsituations mayoccur: MIMOand DC-HSDPAcannot be usedtogether; both64QAM andDC-HSDPA aresupported, butcannot be usedtogether. In thiscase,"MIMO64QA-MorDCHSDPASwitch" is usedto configure thepriorities of thefeatures. Whenthe priority ofMIMO is higherthan that of DC-HSDPA, thepriority of64QAM ishigher than thatof DC-HSDPA.When thepriority of DC-HSDPA ishigher than thatof MIMO, thepriority of DC-HSDPA ishigher than thatof 64QAM.GUI ValueRange:MIMO_



125



64QAM,DC_HSDPAUnit:NoneActual ValueRange:MIMO_64QAM,DC_HSDPADefaultValue:DC_HSDPA



126



MIMO64QA-MorDCHSDPASwitch

BSC6910 SET UFRC WRFD-020400WRFD-010696

DRDIntroductionPackageDC-HSDPA

Meaning:Thisswitch is used toconfigure thepriority ofMIMO_64QAM or DC-HSDPA.According todifferentprotocols, thefollowingsituations mayoccur: MIMOand DC-HSDPAcannot be usedtogether; both64QAM andDC-HSDPA aresupported, butcannot be usedtogether. In thiscase,"MIMO64QA-MorDCHSDPASwitch" is usedto configure thepriorities of thefeatures. Whenthe priority ofMIMO is higherthan that of DC-HSDPA, thepriority of64QAM ishigher than thatof DC-HSDPA.When thepriority of DC-HSDPA ishigher than thatof MIMO, thepriority of DC-HSDPA ishigher than thatof 64QAM.GUI ValueRange:MIMO_



127



64QAM,DC_HSDPAUnit:NoneActual ValueRange:MIMO_64QAM,DC_HSDPADefaultValue:DC_HSDPA



128



CmpSwitch BSC6900 SETUCORRMALGOSWITCH

WRFD-01061006WRFD-020203WRFD-020202WRFD-150209WRFD-150227WRFD-021200WRFD-150223WRFD-010696WRFD-010202WRFD-01061204WRFD-140204WRFD-150250

HSDPAMobilityManagementInter RNC SoftHandoverIntra RNC SoftHandoverDB-HSDPADB-HSDPA+MIMOHCS(HierarchicalCell Structure)MC-HSDPA+MIMODC-HSDPAUE State inConnectedMode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)HSUPAMobilityManagementDC-HSUPA3C-HSDPA

Meaning:1.CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH: When theswitch is on, theIMS signalingassigned by theCN undergoescompatibilityprocessing as anordinary PSservice. Whenthe switch is noton, no specialprocessing isperformed. 2.CMP_IU_QOS_ASYMMETRY_IND_COMPAT_SWITCH:When the IuQoSNegotiationfunction isactive and theswitch is on, IERABAsymmetryIndicator isSymmetricbidirectional,The uplink anddownlink RNCnegotiation rateis asymmetric,"RNC" selectthe bigger rate asIu QoSnegotiation rate.When the switchis OFF, "RNC"select the lessrate as Iu QoSnegotiation rate.3.CMP_IU_SYSHOIN_CMP_I



129



UUP_FIXTO1_SWITCH:When the switchis on, the IUUPversion can berolled back toR99 whencompleteconfigurationsare appliedduring inter-RAT handover.4.CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWITCH:When the switchis on, H2D isperformedbefore aneighboringRNC cell whoseversion is earlierthan R5 is addedto the active set;E2D isperformedbefore aneighboringRNC cell whoseversion is earlierthan R6 is addedto the active set.If the DRNC isof a versionearlier than R5,DL servicescannot bemapped on theHS-DSCH. Ifthe DRNC is of aversion earlierthan R6, DLservices cannotbe mapped onthe HS-EDCH.5.



130



CMP_IUR_SHO_DIVCTRL_SWITCH: Whenthe switch is on,the diversitycombinationover the Iurinterface isconfigured onthe basis of thatof the localRNC. When theswitch is not on,the diversitycombinationover the Iurinterface isconfigured onthe basis ofservices. Theflag of diversitycombinationover the Iurinterface can beset to MUST (forBE services) orMAY (for otherservices). 6.CMP_UU_ADJACENT_FREQ_CM_SWITCH: Whether theRNC activatesthe compressedmode beforeinitiating aninter-frequencymeasurement ona DC-HSDPA orDB-HSDPAUE. When thisparameter is setto ON, the RNCinitiates theinter-frequencymeasurementwithoutactivating the



131



compressedmode if both theUE andEARFCNsupport the non-compressedinter-frequencymeasurement.When thisparameter is setto OFF, the RNCactivates thecompressedmode beforeinitiating theinter-frequencymeasurement.This switchtakes effect onlyin non-flexibleDC cells and DBcells. 7.CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH: Thisparameterspecifies toenable AMRthrough DRDtwo-stepprocedurefunction. WhenSRB is set up onDCH, and"RNC" decidesto setup theAMR throughDRD procedure,When the switchis enabled,"RNC" willexecute blindhandover to thetarget cell, andthen setup theAMR RBs onthe target cell,



132



When the switchis disabled,"RNC" willsetup the AMRRBs on thetarget celldirectly. 8.CMP_UU_AMR_SID_MUST_CFG_SWITCH:For narrowbandAMR services,when the switchis on, the SIDframe is alwaysconfigured;when the switchis not on, theSID frame isconfigured onthe basis of CNassignment. 9.CMP_UU_FDPCH_COMPAT_SWITCH:When the switchis OFF, if theinformationelement thatindicates the F-DPCHcapability of UEexists in themessage"RRC_CONNECT_REQ" or"RRC_CONNECT_SETUP_CMP", the F-DPCHcapabilitydepends on thatindicator. Inother case, itmeans UE doesnot support F-DPCH. Whenthe switch is



133



ON, if theinformationelement thatindicates the F-DPCHcapability of UEexists in themessage"RRC_CONNECT_REQ" or"RRC_CONNECT_SETUP_CMP", the F-DPCHcapabilitydepends on thatindicator. If thatinformationelement does notexist, UEsupports F-DPCH when allthe conditionsmeets: a) theversion of UE isRelease 6. b) UEsupports HS-PDSCH. 10.CMP_UU_IGNORE_UE_RLC_CAP_SWITCH: When theswitch is on, theRABassignmentrequest and thesubsequent RBsetup procedureproceed if theRLC AMcapabilities ofthe UE fail tomeet theminimum RLCTX/RX windowbufferrequirement ofthe RAB to be



134



setup. When theswitch is not on,the RABassignmentrequest isrejected. 11.CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_SWITCH:When thisswitch is on, thecell individualoffset (CIO) ofthe best cell isalways set to 0 inthe INTRA-FREQUENCYMEASUREMENT CONTROLmessages.Otherwise, theCIO informationof the best cell isnot carried in theINTRA-FREQUENCYMEASUREMENT CONTROLmessages. 12.CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWITCH:When the switchis on, the cellsynchronizationinformationtraced by theIOS need to bereported duringthe RRCmeasurementperiod. 13.CMP_UU_SERV_CELL_CHG_WITH_ASU_SWITCH:



135



When the switchis on, the activeset update is inthe sameprocedure as thechange of theserving cell.When the switchis not on, theserving cell ischanged afterthe UE updatesthe active set anddeliversreconfigurationof physicalchannels. Thisswitch isapplicable onlyto R6 oraboveUEs. 14.CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_SWITCH:When the switchis on, channeltransition is inthe sameprocedure as thechange of theserving cell.When the switchis not on, theserving cell ischanged afterthe UE performschanneltransition anddeliversreconfigurationof physicalchannels. 15.CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_SWITCH:By default, the



136



switch is on. Inthis case, theAlternative E-bit is notconfigured forL2. 16.CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH: When theswitch is set toON, only uplinkRLC ordownlink RLCcan be re-establishedduring the statetransition fromCELL_FACH toCELL_FACH(F2F for short).17.CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH: When theswitch is set toON, only uplinkRLC ordownlink RLCcan be re-establishedduring the statetransition fromCELL_DCH toCELL_FACH(D2F for short).18.CMP_RAB_5_CFG_ROHC_SWITCH: Whenthe switch is setto ON, theservice withRAB ID 5 can beconfigured withthe RobustHeader



137



Compression(ROHC)function. Whenthe switch is setto OFF, theservice withRAB ID 5cannot beconfigured withthe ROHCfunction. 19.CMP_RAB_6_CFG_ROHC_SWITCH: Whenthe switch is setto ON, theservice withRAB ID 6 can beconfigured withthe ROHCfunction. Whenthe switch is setto OFF, theservice withRAB ID 6cannot beconfigured withthe ROHCfunction. 20.CMP_RAB_7_CFG_ROHC_SWITCH: Whenthe switch is setto ON, theservice withRAB ID 7 can beconfigured withthe ROHCfunction. Whenthe switch is setto OFF, theservice withRAB ID 7cannot beconfigured withthe ROHCfunction. 21.CMP_RAB_8_



138



CFG_ROHC_SWITCH: Whenthe switch is setto ON, theservice withRAB ID 8 can beconfigured withthe ROHCfunction. Whenthe switch is setto OFF, theservice withRAB ID 8cannot beconfigured withthe ROHCfunction. 22.CMP_RAB_9_CFG_ROHC_SWITCH: Whenthe switch is setto ON, theservice withRAB ID 9 can beconfigured withthe ROHCfunction. Whenthe switch is setto OFF, theservice withRAB ID 9cannot beconfigured withthe ROHCfunction. 23.CMP_HSUPA_MACD_FLOW_MUL_SWITCH: When theswitch is set toON, MAC-dflow can bemultiplexedwithout anyrestrictions.When the switchis set to OFF,only MAC-d



139



flows whoseschedulingpriority is lowerthan that of thecurrent MAC-dflow can bemultiplexed. 24.CMP_SMLC_RSLT_MODE_TYPE_SWITCH:If the ClientType of apositioningrequest is ValueAdded Serviceor LawfulIntercept Client,the positioningresult is reportedby using theEllipsoid Arctype. For otherclient types, thepositioningresult is reportedby using theEllipsoid pointwith uncertaintycircle type. 25.CMP_F2P_PROCESS_OPTIMIZATION_SWITCH: Switchfor optimizingthe procedurefor theCELL_FACH-to-CELL_PCH-or-URA_PCHstate transition.When thisswitch is set toon, F2P statetransition isperformedthrough thephysical channelreconfiguration



140



procedure.When this switch isset to off, F2Pstate transition isperformedthrough the RBreconfigurationprocedure. 26.CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH: Whether tocarry parametersrelated to events1A and 1D insysteminformationblock type 11(SIB 11) andSIB 12.If theswitch ofdeferredmeasurementcontrol readingis turned on, theUE cannotpromptly readparametersrelated to events1A and 1D forintra-frequencyneighboringcells from SIB11 or SIB12. Asa result, the UEcannot performsoft handoversin advance. Theswitch is setusingDeferMcReadInd in the ADD/MODUCELLMEAScommand.GUI ValueRange:CMP_IU



141



_IMS_PROC_AS_NORMAL_PS_SWITCH,CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITCH,CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWITCH,CMP_IUR_SHO_DIVCTRL_SWITCH,CMP_UU_AMR_SID_MUST_CFG_SWITCH,CMP_UU_ADJACENT_FREQ_CM_SWITCH,CMP_UU_IGNORE_UE_RLC_CAP_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_UU_FDPCH_COMPAT_SWITCH,CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH,CMP_IU_QOS_ASYMMETRY_IND_COMPAT_SWITCH,



142



CMP_F2P_PROCESS_OPTIMIZATION_SWITCH,CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWITCH,CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_SWITCH,CMP_UU_SIB11_SIB12_WITH_1A1D_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_SWITCHUnit:None



143



Actual ValueRange: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



144



_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,CMP_F2P_PROCESS_OPTIMIZATION_SWITCH,CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH



145



DefaultValue:CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH:0,CMP_IU_QOS_ASYMMETRY_IND_COMPAT_SWITCH:0,CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITCH:0,CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWITCH:0,CMP_IUR_SHO_DIVCTRL_SWITCH:0,CMP_UU_ADJACENT_FREQ_CM_SWITCH:0,CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH:1,CMP_UU_AMR_SID_MUST_CFG_SWITCH:0,CMP_UU_FDPCH_COMPAT_SWITCH:0,CMP_UU_IGNORE_UE_RLC_CAP_SWITCH:1,CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_SWITCH:0,CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWITCH:0,CMP_UU_SE



146



RV_CELL_CHG_WITH_ASU_SWITCH:0,CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_SWITCH:1,CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_SWITCH:1,CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH:0,CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH:0,CMP_RAB_5_CFG_ROHC_SWITCH:0,CMP_RAB_6_CFG_ROHC_SWITCH:0,CMP_RAB_7_CFG_ROHC_SWITCH:0,CMP_RAB_8_CFG_ROHC_SWITCH:0,CMP_RAB_9_CFG_ROHC_SWITCH:0,CMP_HSUPA_MACD_FLOW_MUL_SWITCH:0,CMP_SMLC_RSLT_MODE_TYPE_SWITCH:0,CMP_F2P_PROCESS_OPTIMIZATION_SWITCH:0,CMP_UU_SI



147



B11_SIB12_WITH_1A1D_SWITCH:0



148



CmpSwitch BSC6910 SETUCORRMALGOSWITCH


HSDPAMobilityManagementInter RNC SoftHandoverIntra RNC SoftHandoverDB-HSDPADB-HSDPA+MIMOHCS(HierarchicalCell Structure)MC-HSDPA+MIMODC-HSDPAUE State inConnectedMode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)HSUPAMobilityManagementDC-HSUPA3C-HSDPA

Meaning:1.CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH: When theswitch is on, theIMS signalingassigned by theCN undergoescompatibilityprocessing as anordinary PSservice. Whenthe switch is noton, no specialprocessing isperformed. 2.CMP_IU_QOS_ASYMMETRY_IND_COMPAT_SWITCH:When the IuQoSNegotiationfunction isactive and theswitch is on, IERABAsymmetryIndicator isSymmetricbidirectional,The uplink anddownlink RNCnegotiation rateis asymmetric,"RNC" selectthe bigger rate asIu QoSnegotiation rate.When the switchis OFF, "RNC"select the lessrate as Iu QoSnegotiation rate.3.CMP_IU_SYSHOIN_CMP_I



149



UUP_FIXTO1_SWITCH:When the switchis on, the IUUPversion can berolled back toR99 whencompleteconfigurationsare appliedduring inter-RAT handover.4.CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWITCH:When the switchis on, H2D isperformedbefore aneighboringRNC cell whoseversion is earlierthan R5 is addedto the active set;E2D isperformedbefore aneighboringRNC cell whoseversion is earlierthan R6 is addedto the active set.If the DRNC isof a versionearlier than R5,DL servicescannot bemapped on theHS-DSCH. Ifthe DRNC is of aversion earlierthan R6, DLservices cannotbe mapped onthe HS-EDCH.5.



150



CMP_IUR_SHO_DIVCTRL_SWITCH: Whenthe switch is on,the diversitycombinationover the Iurinterface isconfigured onthe basis of thatof the localRNC. When theswitch is not on,the diversitycombinationover the Iurinterface isconfigured onthe basis ofservices. Theflag of diversitycombinationover the Iurinterface can beset to MUST (forBE services) orMAY (for otherservices). 6.CMP_UU_ADJACENT_FREQ_CM_SWITCH: Whether theRNC activatesthe compressedmode beforeinitiating aninter-frequencymeasurement ona DC-HSDPA orDB-HSDPAUE. When thisparameter is setto ON, the RNCinitiates theinter-frequencymeasurementwithoutactivating the



151



compressedmode if both theUE andEARFCNsupport the non-compressedinter-frequencymeasurement.When thisparameter is setto OFF, the RNCactivates thecompressedmode beforeinitiating theinter-frequencymeasurement.This switchtakes effect onlyin non-flexibleDC cells and DBcells. 7.CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH: Thisparameterspecifies toenable AMRthrough DRDtwo-stepprocedurefunction. WhenSRB is set up onDCH, and"RNC" decidesto setup theAMR throughDRD procedure,When the switchis enabled,"RNC" willexecute blindhandover to thetarget cell, andthen setup theAMR RBs onthe target cell,



152



When the switchis disabled,"RNC" willsetup the AMRRBs on thetarget celldirectly. 8.CMP_UU_AMR_SID_MUST_CFG_SWITCH:For narrowbandAMR services,when the switchis on, the SIDframe is alwaysconfigured;when the switchis not on, theSID frame isconfigured onthe basis of CNassignment. 9.CMP_UU_FDPCH_COMPAT_SWITCH:When the switchis OFF, if theinformationelement thatindicates the F-DPCHcapability of UEexists in themessage"RRC_CONNECT_REQ" or"RRC_CONNECT_SETUP_CMP", the F-DPCHcapabilitydepends on thatindicator. Inother case, itmeans UE doesnot support F-DPCH. Whenthe switch is



153



ON, if theinformationelement thatindicates the F-DPCHcapability of UEexists in themessage"RRC_CONNECT_REQ" or"RRC_CONNECT_SETUP_CMP", the F-DPCHcapabilitydepends on thatindicator. If thatinformationelement does notexist, UEsupports F-DPCH when allthe conditionsmeets: a) theversion of UE isRelease 6. b) UEsupports HS-PDSCH. 10.CMP_UU_IGNORE_UE_RLC_CAP_SWITCH: When theswitch is on, theRABassignmentrequest and thesubsequent RBsetup procedureproceed if theRLC AMcapabilities ofthe UE fail tomeet theminimum RLCTX/RX windowbufferrequirement ofthe RAB to be



154



setup. When theswitch is not on,the RABassignmentrequest isrejected. 11.CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_SWITCH:When thisswitch is on, thecell individualoffset (CIO) ofthe best cell isalways set to 0 inthe INTRA-FREQUENCYMEASUREMENT CONTROLmessages.Otherwise, theCIO informationof the best cell isnot carried in theINTRA-FREQUENCYMEASUREMENT CONTROLmessages. 12.CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWITCH:When the switchis on, the cellsynchronizationinformationtraced by theIOS need to bereported duringthe RRCmeasurementperiod. 13.CMP_UU_SERV_CELL_CHG_WITH_ASU_SWITCH:



155



When the switchis on, the activeset update is inthe sameprocedure as thechange of theserving cell.When the switchis not on, theserving cell ischanged afterthe UE updatesthe active set anddeliversreconfigurationof physicalchannels. Thisswitch isapplicable onlyto R6 oraboveUEs. 14.CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_SWITCH:When the switchis on, channeltransition is inthe sameprocedure as thechange of theserving cell.When the switchis not on, theserving cell ischanged afterthe UE performschanneltransition anddeliversreconfigurationof physicalchannels. 15.CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_SWITCH:By default, the



156



switch is on. Inthis case, theAlternative E-bit is notconfigured forL2. 16.CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH: When theswitch is set toON, only uplinkRLC ordownlink RLCcan be re-establishedduring the statetransition fromCELL_FACH toCELL_FACH(F2F for short).17.CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH: When theswitch is set toON, only uplinkRLC ordownlink RLCcan be re-establishedduring the statetransition fromCELL_DCH toCELL_FACH(D2F for short).18.CMP_RAB_5_CFG_ROHC_SWITCH: Whenthe switch is setto ON, theservice withRAB ID 5 can beconfigured withthe RobustHeader



157



Compression(ROHC)function. Whenthe switch is setto OFF, theservice withRAB ID 5cannot beconfigured withthe ROHCfunction. 19.CMP_RAB_6_CFG_ROHC_SWITCH: Whenthe switch is setto ON, theservice withRAB ID 6 can beconfigured withthe ROHCfunction. Whenthe switch is setto OFF, theservice withRAB ID 6cannot beconfigured withthe ROHCfunction. 20.CMP_RAB_7_CFG_ROHC_SWITCH: Whenthe switch is setto ON, theservice withRAB ID 7 can beconfigured withthe ROHCfunction. Whenthe switch is setto OFF, theservice withRAB ID 7cannot beconfigured withthe ROHCfunction. 21.CMP_RAB_8_



158



CFG_ROHC_SWITCH: Whenthe switch is setto ON, theservice withRAB ID 8 can beconfigured withthe ROHCfunction. Whenthe switch is setto OFF, theservice withRAB ID 8cannot beconfigured withthe ROHCfunction. 22.CMP_RAB_9_CFG_ROHC_SWITCH: Whenthe switch is setto ON, theservice withRAB ID 9 can beconfigured withthe ROHCfunction. Whenthe switch is setto OFF, theservice withRAB ID 9cannot beconfigured withthe ROHCfunction. 23.CMP_HSUPA_MACD_FLOW_MUL_SWITCH: When theswitch is set toON, MAC-dflow can bemultiplexedwithout anyrestrictions.When the switchis set to OFF,only MAC-d



159



flows whoseschedulingpriority is lowerthan that of thecurrent MAC-dflow can bemultiplexed. 24.CMP_SMLC_RSLT_MODE_TYPE_SWITCH:If the ClientType of apositioningrequest is ValueAdded Serviceor LawfulIntercept Client,the positioningresult is reportedby using theEllipsoid Arctype. For otherclient types, thepositioningresult is reportedby using theEllipsoid pointwith uncertaintycircle type. 25.CMP_F2P_PROCESS_OPTIMIZATION_SWITCH: Switchfor optimizingthe procedurefor theCELL_FACH-to-CELL_PCH-or-URA_PCHstate transition.When thisswitch is set toon, F2P statetransition isperformedthrough thephysical channelreconfiguration



160



procedure.When this switch isset to off, F2Pstate transition isperformedthrough the RBreconfigurationprocedure. 26.CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH: Whether tocarry parametersrelated to events1A and 1D insysteminformationblock type 11(SIB 11) andSIB 12.If theswitch ofdeferredmeasurementcontrol readingis turned on, theUE cannotpromptly readparametersrelated to events1A and 1D forintra-frequencyneighboringcells from SIB11 or SIB12. Asa result, the UEcannot performsoft handoversin advance. Theswitch is setusingDeferMcReadInd in the ADD/MODUCELLMEAScommand.GUI ValueRange:CMP_IU



161



_IMS_PROC_AS_NORMAL_PS_SWITCH,CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITCH,CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWITCH,CMP_IUR_SHO_DIVCTRL_SWITCH,CMP_UU_AMR_SID_MUST_CFG_SWITCH,CMP_UU_ADJACENT_FREQ_CM_SWITCH,CMP_UU_IGNORE_UE_RLC_CAP_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_UU_FDPCH_COMPAT_SWITCH,CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH,CMP_IU_QOS_ASYMMETRY_IND_COMPAT_SWITCH,



162



CMP_F2P_PROCESS_OPTIMIZATION_SWITCH,CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWITCH,CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_SWITCH,CMP_UU_SIB11_SIB12_WITH_1A1D_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_SWITCHUnit:None



163



Actual ValueRange: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



164



_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,CMP_F2P_PROCESS_OPTIMIZATION_SWITCH,CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH



165



DefaultValue:CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH:0,CMP_IU_QOS_ASYMMETRY_IND_COMPAT_SWITCH:0,CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITCH:0,CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWITCH:0,CMP_IUR_SHO_DIVCTRL_SWITCH:0,CMP_UU_ADJACENT_FREQ_CM_SWITCH:0,CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH:1,CMP_UU_AMR_SID_MUST_CFG_SWITCH:0,CMP_UU_FDPCH_COMPAT_SWITCH:0,CMP_UU_IGNORE_UE_RLC_CAP_SWITCH:1,CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_SWITCH:0,CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWITCH:0,CMP_UU_SE



166



RV_CELL_CHG_WITH_ASU_SWITCH:0,CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_SWITCH:1,CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_SWITCH:1,CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH:0,CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH:0,CMP_RAB_5_CFG_ROHC_SWITCH:0,CMP_RAB_6_CFG_ROHC_SWITCH:0,CMP_RAB_7_CFG_ROHC_SWITCH:0,CMP_RAB_8_CFG_ROHC_SWITCH:0,CMP_RAB_9_CFG_ROHC_SWITCH:0,CMP_HSUPA_MACD_FLOW_MUL_SWITCH:0,CMP_SMLC_RSLT_MODE_TYPE_SWITCH:0,CMP_F2P_PROCESS_OPTIMIZATION_SWITCH:0,CMP_UU_SI



167



B11_SIB12_WITH_1A1D_SWITCH:0



168



ChannelRetryHoTimerLen

BSC6900 SETUCOIFTIMER


HSUPA 2msTTIDynamicChannelConfigurationControl (DCCC)DownlinkEnhanced L2SRB overHSDPACPC - DTX /DRXCPC - HS-SCCH lessoperation2x2 MIMOHSUPA 2ms/10ms TTIHandoverDownlink64QAMDB-HSDPASRB overHSUPAHCS(HierarchicalCell Structure)

Meaning:Thisparameterspecifies thevalue of thechannel retryhandover timer.When handoveris performed andsome higherHSPA or HSPAplus technique issupported,UTRAN willtrigger thereconfigurationfor the highertechniques.Pingpang willhappen when thereconfigurationis triggeredimmediatelywhen handoversucceeds,becausehandoverprocedure isfrequently. Inorder to avoidthe pingpang,this timer willstart afterhandoverprocedure isperformed, andthereconfigurationwill not betriggered untilthe timerexpires.GUI ValueRange:0~999Unit:sActual ValueRange:0~999



169



Default Value:2



170



ChannelRetryHoTimerLen



HSUPA 2msTTIDynamicChannelConfigurationControl (DCCC)DownlinkEnhanced L2SRB overHSDPACPC - DTX /DRXCPC - HS-SCCH lessoperation2x2 MIMOHSUPA 2ms/10ms TTIHandoverDownlink64QAMDB-HSDPASRB overHSUPAHCS(HierarchicalCell Structure)

Meaning:Thisparameterspecifies thevalue of thechannel retryhandover timer.When handoveris performed andsome higherHSPA or HSPAplus technique issupported,UTRAN willtrigger thereconfigurationfor the highertechniques.Pingpang willhappen when thereconfigurationis triggeredimmediatelywhen handoversucceeds,becausehandoverprocedure isfrequently. Inorder to avoidthe pingpang,this timer willstart afterhandoverprocedure isperformed, andthereconfigurationwill not betriggered untilthe timerexpires.GUI ValueRange:0~999Unit:sActual ValueRange:0~999



171



Default Value:2



172



ChannelRetryTimerLen


WRFD-01061403WRFD-021101WRFD-010694WRFD-010693WRFD-150207WRFD-010652WRFD-010686WRFD-010687WRFD-010684WRFD-010685WRFD-010683WRFD-01061008WRFD-150209WRFD-01061206WRFD-140204WRFD-010696WRFD-150250WRFD-010636WRFD-010630WRFD-010632WRFD-01061112

HSUPA 2msTTI

DynamicChannelConfigurationControl (DCCC)

UL 16QAM

DL 64QAM+MIMO

4C-HSDPA

SRB overHSDPA

CPC - DTX /DRX


2x2 MIMO

DownlinkEnhanced L2

Downlink64QAM


DB-HSDPA


DC-HSUPA

DC-HSDPA

3C-HSDPA

SRB overHSUPA

StreamingTraffic Class onHSDPA

StreamingTraffic Class onHSUPA

Meaning:Thisparameterspecifies thevalue of thechannel retrytimer. The timerwill start whentraffic is set upor reconfiguredand some highertechnique is notconfigured bysome reasonexcept for thecapability of UEor cell. Channelretry will beperformed afterthis timerexpires.GUI ValueRange:0~180Unit:sActual ValueRange:0~180Default Value:5



173



HSDPA DRD



174



ChannelRetryTimerLen


WRFD-01061403WRFD-021101WRFD-010694WRFD-010693WRFD-150207WRFD-010652WRFD-010686WRFD-010687WRFD-010684WRFD-010685WRFD-010683WRFD-01061008WRFD-150209WRFD-01061206WRFD-140204WRFD-010696WRFD-150250WRFD-010636WRFD-010630WRFD-010632WRFD-01061112

HSUPA 2msTTI

DynamicChannelConfigurationControl (DCCC)

UL 16QAM

DL 64QAM+MIMO

4C-HSDPA

SRB overHSDPA

CPC - DTX /DRX


2x2 MIMO

DownlinkEnhanced L2

Downlink64QAM


DB-HSDPA


DC-HSUPA

DC-HSDPA

3C-HSDPA

SRB overHSUPA

StreamingTraffic Class onHSDPA

StreamingTraffic Class onHSUPA

Meaning:Thisparameterspecifies thevalue of thechannel retrytimer. The timerwill start whentraffic is set upor reconfiguredand some highertechnique is notconfigured bysome reasonexcept for thecapability of UEor cell. Channelretry will beperformed afterthis timerexpires.GUI ValueRange:0~180Unit:sActual ValueRange:0~180Default Value:5



175



HSDPA DRD



176



RetryCapability BSC6900 SET UFRC WRFD-01061403WRFD-010699WRFD-150207WRFD-010652WRFD-010686WRFD-010687WRFD-010684WRFD-010685WRFD-010695WRFD-010683WRFD-010697WRFD-010694WRFD-150227WRFD-150209WRFD-150250WRFD-010636WRFD-010696WRFD-150223WRFD-010693

HSUPA 2msTTIDC-HSDPA+MIMO4C-HSDPASRB overHSDPACPC - DTX /DRXCPC - HS-SCCH lessoperation2x2 MIMODownlinkEnhanced L2UL Layer 2ImprovementDownlink64QAME-DPCCHBoostingUL 16QAMDB-HSDPA+MIMODB-HSDPA3C-HSDPASRB overHSUPADC-HSDPAMC-HSDPA+MIMODL 64QAM+MIMO

Meaning:Thisparameterspecifies whichHSPAtechnologies canbe retried byUEs. When theHSPAtechnologies areselected andcurrently UE isnot using them,"RNC" willinitiate theseHSPAtechnologiesretry 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,DC_HSUPA,HSDPA_4C_MIMO,HSDPA_4C,DBMIMO_HS



177



DPA,DB_HSDPAUnit:NoneActual 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,DC_HSUPA,HSDPA_4C_MIMO,HSDPA_4C,DBMIMO_HSDPA,DB_HSDPADefaultValue:SRB_OVER_HSDPA:0,SRB_OVER_HSUPA:0,TTI_2MS:0,MIMO:1,64QAM:1,DL_L2_ENHANCE:1,DTX_DRX:1,HSSCCH_LESS_OPERATIO



178



N:1,MIMO_64QAM:0,DC_HSDPA:0,UL_L2_ENHANCE:0,UL_16QAM:0,EDPCCH_BOOSTING:0,DCMIMO_HSDPA:0,DC_HSUPA:0,HSDPA_4C_MIMO:0,HSDPA_4C:0,DBMIMO_HSDPA:0,DB_HSDPA:0



179



RetryCapability BSC6910 SET UFRC WRFD-01061403WRFD-010699WRFD-150207WRFD-010652WRFD-010686WRFD-010687WRFD-010684WRFD-010685WRFD-010695WRFD-010683WRFD-010697WRFD-010694WRFD-150227WRFD-150209WRFD-150250WRFD-010636WRFD-010696WRFD-150223WRFD-010693

HSUPA 2msTTIDC-HSDPA+MIMO4C-HSDPASRB overHSDPACPC - DTX /DRXCPC - HS-SCCH lessoperation2x2 MIMODownlinkEnhanced L2UL Layer 2ImprovementDownlink64QAME-DPCCHBoostingUL 16QAMDB-HSDPA+MIMODB-HSDPA3C-HSDPASRB overHSUPADC-HSDPAMC-HSDPA+MIMODL 64QAM+MIMO

Meaning:Thisparameterspecifies whichHSPAtechnologies canbe retried byUEs. When theHSPAtechnologies areselected andcurrently UE isnot using them,"RNC" willinitiate theseHSPAtechnologiesretry 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,DC_HSUPA,HSDPA_4C_MIMO,HSDPA_4C,DBMIMO_HS



180



DPA,DB_HSDPAUnit:NoneActual 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,DC_HSUPA,HSDPA_4C_MIMO,HSDPA_4C,DBMIMO_HSDPA,DB_HSDPADefaultValue:SRB_OVER_HSDPA:0,SRB_OVER_HSUPA:0,TTI_2MS:0,MIMO:1,64QAM:1,DL_L2_ENHANCE:1,DTX_DRX:1,HSSCCH_LESS_OPERATIO



181



N:1,MIMO_64QAM:0,DC_HSDPA:0,UL_L2_ENHANCE:0,UL_16QAM:0,EDPCCH_BOOSTING:0,DCMIMO_HSDPA:0,DC_HSUPA:0,HSDPA_4C_MIMO:0,HSDPA_4C:0,DBMIMO_HSDPA:0,DB_HSDPA:0



182



ULLdbDRD-SwitchDcHSDPA

BSC6900 ADDUCELLDRDMODUCELLDRD

WRFD-02040004

Traffic Steeringand LoadSharing DuringRAB Setup

Meaning:Whether DC-HSDPAUEs enable theuplink loadbalancingalgorithm toselect a cell withthe primarycarrier duringthe access. If thisswitch is turnedon and theserving cell hasthe samedownlink loadas a neighboringcell during loadbalancing DRDfor HSDPAservices, theRNC selects thecell with theprimary carrieraccording to thenumber ofuplinkequivalent usersadmitted to theprimary servingcell and theuplink load ofthe targetneighboringcell.GUI ValueRange:OFF, ONUnit:NoneActual ValueRange:ON, OFFDefaultValue:OFF



183



ULLdbDRD-SwitchDcHSDPA


WRFD-02040004


Meaning:Whether DC-HSDPAUEs enable theuplink loadbalancingalgorithm toselect a cell withthe primarycarrier duringthe access. If thisswitch is turnedon and theserving cell hasthe samedownlink loadas a neighboringcell during loadbalancing DRDfor HSDPAservices, theRNC selects thecell with theprimary carrieraccording to thenumber ofuplinkequivalent usersadmitted to theprimary servingcell and theuplink load ofthe targetneighboringcell.GUI ValueRange:OFF, ONUnit:NoneActual ValueRange:ON, OFFDefaultValue:OFF



184



ULLdbDRDLoadRemainThdDcHSDPA


WRFD-02040004


Meaning:Loadthreshold forDC-HSDPAUEs to triggerload balanceDRD in theuplink. If theremainingnumber ofequivalent usersin the uplink isless than thevalue of thisparameter whenDC-HSDPAUEs access thecell, loadbalancing DRDis triggered forDC-HSDPAUEs and thetarget DC cellwith a largerremainingnumber ofequivalent usersin the uplink isselected as theprimary-carriercell for DC-HSDPA UEs.GUI ValueRange:0~100Unit:%Actual ValueRange:0~100Default Value:25



185



ULLdbDRDLoadRemainThdDcHSDPA


WRFD-02040004


Meaning:Loadthreshold forDC-HSDPAUEs to triggerload balanceDRD in theuplink. If theremainingnumber ofequivalent usersin the uplink isless than thevalue of thisparameter whenDC-HSDPAUEs access thecell, loadbalancing DRDis triggered forDC-HSDPAUEs and thetarget DC cellwith a largerremainingnumber ofequivalent usersin the uplink isselected as theprimary-carriercell for DC-HSDPA UEs.GUI ValueRange:0~100Unit:%Actual ValueRange:0~100Default Value:25



186



ULLdbDRDOffsetDcHSDPA

BSC6900 SET UDRD WRFD-02040004


Meaning:Available uplinkequivalent usernumber offsetused to select adirect retrycandidate cellwhen uplinkload balancingDRD algorithmis activated forHSDPA traffic.If the differenceof the availableremainingnumber ofuplinkequivalent usersbetween thetarget cell andthe serving cellis greater thanthe value of thisparameter, thetarget cellsatisfiesconditions for adirect retrycandidate cell.GUI ValueRange:0~100Unit:%Actual ValueRange:0~100Default Value:10



187



ULLdbDRDOffsetDcHSDPA

BSC6910 SET UDRD WRFD-02040004


Meaning:Available uplinkequivalent usernumber offsetused to select adirect retrycandidate cellwhen uplinkload balancingDRD algorithmis activated forHSDPA traffic.If the differenceof the availableremainingnumber ofuplinkequivalent usersbetween thetarget cell andthe serving cellis greater thanthe value of thisparameter, thetarget cellsatisfiesconditions for adirect retrycandidate cell.GUI ValueRange:0~100Unit:%Actual ValueRange:0~100Default Value:10



188



MULTICELLGRPTYPE

BTS3900,BTS3900WCDMA

ADDNODEBMULTICELLGRPLSTNODEBMULTICELLGRP

WRFD-010696WRFD-140204WRFD-150209WRFD-150207WRFD-150250WRFD-150208WRFD-150223WRFD-150227WRFD-010699

DC-HSDPADC-HSUPADB-HSDPA4C-HSDPA3C-HSDPAFlexible DualCarrier HSDPAMC-HSDPA+MIMODB-HSDPA+MIMODC-HSDPA+MIMO

Meaning:Speci-fies the type of amultiple carriercell group.GUI ValueRange:HSDPA(HSDPA),HSUPA(HSUPA)Unit:NoneActual ValueRange:HSDPA,HSUPADefaultValue:HSDPA(HSDPA)

MULTICELLGRPID


ADDNODEBMULTICELLGRPADDNODEBMULTICELLGRPITEMLSTNODEBMULTICELLGRPLSTNODEBMULTICELLGRPITEMRMVNODEBMULTICELLGRPRMVNODEBMULTICELLGRPITEM

None None Meaning:Uniquely identifies amultiple carriercell group.GUI ValueRange:0~95Unit:NoneActual ValueRange:0~95DefaultValue:None



189



ULOCELLID BTS3900,BTS3900WCDMA

ADDULOCELLADDULOCELLBBUNITBLKULOCELLDSP ULOCELLDSPULOCELLDESENSDSPULOCELLRESLST ULOCELLLSTULOCELLBBUNITLSTULOCELLPRILSTULOCELLTLMODULOCELLRMVULOCELLRMVULOCELLBBUNITSETULOCELLDESENSSETULOCELLPRISETULOCELLTLUBLULOCELL

None None Meaning:Indi-cates the LocalCell ID. Thelocal cell ID isunique for oneNodeB.GUI ValueRange:0~268435455Unit:NoneActual ValueRange:0~268435455DefaultValue:None



190



MapSwitch BSC6900 SETUCORRMALGOSWITCH


HSUPA 2msTTI3.4/6.8/13.6/27.2Kbps RRCConnection andRadio AccessBearerEstablishmentand ReleaseDownlinkEnhancedCELL_FACHSRB overHSDPARateNegotiation atAdmissionControlSRB overHSUPACombination ofOne CS Serviceand One PSServiceStreamingTraffic Class onHSUPAStreamingTraffic Class onHSDPA

Meaning:Service mappingstrategy switchgroup. 1.MAP_HSUPA_TTI_2MS_SWITCH: When theswitch is on, 2ms TTI issupported forHSUPA. 2.MAP_INTER_RAT_PS_IN_CHANLE_LIMIT_SWITCH:Whether toconsistentlyallocate DCHsto servicesdiverted to thecurrent networkthroughincoming inter-RAT handovers.When thisswitch is turnedon, the RNCconsistentlyallocates DCHsto such services.When thisswitch is turnedoff, the RNCselectsappropriatechannels to suchservices. 3.MAP_PS_BE_ON_E_FACH_SWITCH:When the switchis on, the PS BEservices can betransmitted onthe E-FACH(E-FACH fordownlink andRACH for



191



uplink, or E-FACH fordownlink and E-RACH foruplink). 4.MAP_PS_STREAM_ON_E_FACH_SWITCH: When theswitch is on, thePS streamingservices can betransmitted onthe E-FACH(E-FACH fordownlink andRACH foruplink, or E-FACH fordownlink and E-RACH foruplink). 5.MAP_PS_STREAM_ON_HSDPA_SWITCH:When the switchis on, a PSstreamingservice ismapped on theHS-DSCH if theDL maximumrate of theservice is greaterthan or equal tothe HSDPAthreshold forstreamingservices. 6.MAP_PS_STREAM_ON_HSUPA_SWITCH:When the switchis on, a PSstreamingservice ismapped on theE-DCH if the



192



UL maximumrate of theservice is greaterthan or equal tothe HSUPAthreshold forstreamingservices. 7.MAP_SRB_6800_WHEN_RAB_ON_HSDSCH_SWITCH:When the switchis on, thesignaling istransmitted at arate of 6.8 kbit/sif all thedownlink trafficis on the HSDPAchannel. 8.MAP_SRB_ON_DCH_OR_FACH_CS_RRC_SWITCH:When thisswitch is turnedon, the SRB of aCS RRCconnectioncannot beestablished onHSPA channels.The RNCdetermineswhether an RRCconnectionrequest is for aCS servicebased on theRRC connectionsetup cause andthe value ofDomainIndicator. For aUE of a versionearlier thanRelease 6, the



193



RRC connectionsetup cause ofCS services isOriginatingConversationalCall orTerminatingConversationalCall. For a UE ofRelease 6 or alater version, thevalue of DomainIndicator mustbe CS and theRRC connectionsetup cause mustbe OriginatingConversationalCall orTerminatingConversationalCall for a CSservice. 9.MAP_CSPS_TTI_2MS_LIMIT_SWITCH:Whether CS andPS combinedservices can useHSUPA 2mstransmissiontime interval(TTI). When thisswitch is turnedon, CS and PScombinedservices cannotuse HSUPA 2msTTI, whichreduces CS calldrops caused byTTI switching.When thisswitch is turnedoff, CS and PScombinedservices can useHSUPA 2ms



194



TTI. 10.MAP_CSPS_PS_UL_USE_DCH_SWITCH:Whether uplinkPS services ofCS and PScombinedservices arecarried onDCHs. Whenthis switch isturned off, theRNC determinesthe channel forcarrying uplinkservices of CSand PScombinedservices. Whenthis switch isturned on andCS and PScombinedservicesexisting, theuplink PSservices must becarried onDCHs. 11.MAP_CSPS_PS_DL_USE_DCH_SWITCH:Whetherdownlink PSservices of CSand PScombinedservices arecarried onDCHs. Whenthis switch isturned off, theRNC determinesthe channelcarrying thedownlink PSservices of the



195



CS and PScombinedservices. Whenthis switch isturned on andCS and PScombinedservicesexisting, thedownlink PSservices must becarried onDCHs. 12.MAP_CSPS_MC_LIMIT_SWITCH: Whetherto allow UEs toperform CS+PScombinedservices usingMCHSPA.Whenthis switch isturned on, UEsare not allowedto perform CS+PS combinedservices usingMC HSPA (MCstands for multi-carrier.) Thisprevents calldrops that arecaused byfrequentreconfigurationsin areasbordered by MCand non-MCcells.When thisswitch is turnedoff, UEs areallowed toperform CS+PScombinedservices usingMC HSPA. 13.MAP_CSPS_R



196



L_RESET_0K_LIMIT_SWITCH: Whether toallocate a 0 kbit/s DCH to the PSservice of CS+PS combinedservices duringlinkreestablishmentWhen thisswitch is turnedon, a 0 kbit/sDCH isallocated to thePS service of CS+PS combinedservices duringlinkreestablishmentand the data rateof the CS serviceremainsunchanged. Thisprevents calldrops in case ofpoor coverage.GUI ValueRange:MAP_HSUPA_TTI_2MS_SWITCH,MAP_INTER_RAT_PS_IN_CHANLE_LIMIT_SWITCH,MAP_PS_BE_ON_E_FACH_SWITCH,MAP_PS_STREAM_ON_E_FACH_SWITCH,MAP_PS_STREAM_ON_HSDPA_SWITCH,MAP_PS_STREAM_ON_HS



197



UPA_SWITCH,MAP_SRB_6800_WHEN_RAB_ON_HSDSCH_SWITCH,MAP_SRB_ON_DCH_OR_FACH_CS_RRC_SWITCH,MAP_CSPS_TTI_2MS_LIMIT_SWITCH,MAP_CSPS_PS_UL_USE_DCH_SWITCH,MAP_CSPS_PS_DL_USE_DCH_SWITCH,MAP_CSPS_MC_LIMIT_SWITCH,MAP_CSPS_RL_RESET_0K_LIMIT_SWITCHUnit:NoneActual ValueRange:MAP_HSUPA_TTI_2MS_SWITCH,MAP_INTER_RAT_PS_IN_CHANLE_LIMIT_SWITCH,MAP_PS_BE_ON_E_FACH_SWITCH,MAP_PS_STREAM_ON_E_FACH_SWITCH,MAP_PS_STREAM_ON_HSDPA_SWITCH,MAP_PS_STREAM_ON_HSUPA_SWITCH,



198



MAP_SRB_6800_WHEN_RAB_ON_HSDSCH_SWITCH,MAP_SRB_ON_DCH_OR_FACH_CS_RRC_SWITCH,MAP_CSPS_TTI_2MS_LIMIT_SWITCH,MAP_CSPS_PS_UL_USE_DCH_SWITCH,MAP_CSPS_PS_DL_USE_DCH_SWITCH,MAP_CSPS_MC_LIMIT_SWITCH,MAP_CSPS_RL_RESET_0K_LIMIT_SWITCHDefaultValue:MAP_HSUPA_TTI_2MS_SWITCH:0,MAP_INTER_RAT_PS_IN_CHANLE_LIMIT_SWITCH:0,MAP_PS_BE_ON_E_FACH_SWITCH:0,MAP_PS_STREAM_ON_E_FACH_SWITCH:0,MAP_PS_STREAM_ON_HSDPA_SWITCH:0,MAP_PS_STREAM_ON_HSUPA_SWITCH:0,MAP_SRB_6800_WHEN_R



199



AB_ON_HSDSCH_SWITCH:0,MAP_SRB_ON_DCH_OR_FACH_CS_RRC_SWITCH:1,MAP_CSPS_TTI_2MS_LIMIT_SWITCH:0,MAP_CSPS_PS_UL_USE_DCH_SWITCH:1,MAP_CSPS_PS_DL_USE_DCH_SWITCH:0,MAP_CSPS_MC_LIMIT_SWITCH:0,MAP_CSPS_RL_RESET_0K_LIMIT_SWITCH:0



200



MapSwitch BSC6910 SETUCORRMALGOSWITCH


HSUPA 2msTTI3.4/6.8/13.6/27.2Kbps RRCConnection andRadio AccessBearerEstablishmentand ReleaseDownlinkEnhancedCELL_FACHSRB overHSDPARateNegotiation atAdmissionControlSRB overHSUPACombination ofOne CS Serviceand One PSServiceStreamingTraffic Class onHSUPAStreamingTraffic Class onHSDPA

Meaning:Service mappingstrategy switchgroup. 1.MAP_HSUPA_TTI_2MS_SWITCH: When theswitch is on, 2ms TTI issupported forHSUPA. 2.MAP_INTER_RAT_PS_IN_CHANLE_LIMIT_SWITCH:Whether toconsistentlyallocate DCHsto servicesdiverted to thecurrent networkthroughincoming inter-RAT handovers.When thisswitch is turnedon, the RNCconsistentlyallocates DCHsto such services.When thisswitch is turnedoff, the RNCselectsappropriatechannels to suchservices. 3.MAP_PS_BE_ON_E_FACH_SWITCH:When the switchis on, the PS BEservices can betransmitted onthe E-FACH(E-FACH fordownlink andRACH for



201



uplink, or E-FACH fordownlink and E-RACH foruplink). 4.MAP_PS_STREAM_ON_E_FACH_SWITCH: When theswitch is on, thePS streamingservices can betransmitted onthe E-FACH(E-FACH fordownlink andRACH foruplink, or E-FACH fordownlink and E-RACH foruplink). 5.MAP_PS_STREAM_ON_HSDPA_SWITCH:When the switchis on, a PSstreamingservice ismapped on theHS-DSCH if theDL maximumrate of theservice is greaterthan or equal tothe HSDPAthreshold forstreamingservices. 6.MAP_PS_STREAM_ON_HSUPA_SWITCH:When the switchis on, a PSstreamingservice ismapped on theE-DCH if the



202



UL maximumrate of theservice is greaterthan or equal tothe HSUPAthreshold forstreamingservices. 7.MAP_SRB_6800_WHEN_RAB_ON_HSDSCH_SWITCH:When the switchis on, thesignaling istransmitted at arate of 6.8 kbit/sif all thedownlink trafficis on the HSDPAchannel. 8.MAP_SRB_ON_DCH_OR_FACH_CS_RRC_SWITCH:When thisswitch is turnedon, the SRB of aCS RRCconnectioncannot beestablished onHSPA channels.The RNCdetermineswhether an RRCconnectionrequest is for aCS servicebased on theRRC connectionsetup cause andthe value ofDomainIndicator. For aUE of a versionearlier thanRelease 6, the



203



RRC connectionsetup cause ofCS services isOriginatingConversationalCall orTerminatingConversationalCall. For a UE ofRelease 6 or alater version, thevalue of DomainIndicator mustbe CS and theRRC connectionsetup cause mustbe OriginatingConversationalCall orTerminatingConversationalCall for a CSservice. 9.MAP_CSPS_TTI_2MS_LIMIT_SWITCH:Whether CS andPS combinedservices can useHSUPA 2mstransmissiontime interval(TTI). When thisswitch is turnedon, CS and PScombinedservices cannotuse HSUPA 2msTTI, whichreduces CS calldrops caused byTTI switching.When thisswitch is turnedoff, CS and PScombinedservices can useHSUPA 2ms



204



TTI. 10.MAP_CSPS_PS_UL_USE_DCH_SWITCH:Whether uplinkPS services ofCS and PScombinedservices arecarried onDCHs. Whenthis switch isturned off, theRNC determinesthe channel forcarrying uplinkservices of CSand PScombinedservices. Whenthis switch isturned on andCS and PScombinedservicesexisting, theuplink PSservices must becarried onDCHs. 11.MAP_CSPS_PS_DL_USE_DCH_SWITCH:Whetherdownlink PSservices of CSand PScombinedservices arecarried onDCHs. Whenthis switch isturned off, theRNC determinesthe channelcarrying thedownlink PSservices of the



205



CS and PScombinedservices. Whenthis switch isturned on andCS and PScombinedservicesexisting, thedownlink PSservices must becarried onDCHs. 12.MAP_CSPS_MC_LIMIT_SWITCH: Whetherto allow UEs toperform CS+PScombinedservices usingMCHSPA.Whenthis switch isturned on, UEsare not allowedto perform CS+PS combinedservices usingMC HSPA (MCstands for multi-carrier.) Thisprevents calldrops that arecaused byfrequentreconfigurationsin areasbordered by MCand non-MCcells.When thisswitch is turnedoff, UEs areallowed toperform CS+PScombinedservices usingMC HSPA. 13.MAP_CSPS_R



206



L_RESET_0K_LIMIT_SWITCH: Whether toallocate a 0 kbit/s DCH to the PSservice of CS+PS combinedservices duringlinkreestablishmentWhen thisswitch is turnedon, a 0 kbit/sDCH isallocated to thePS service of CS+PS combinedservices duringlinkreestablishmentand the data rateof the CS serviceremainsunchanged. Thisprevents calldrops in case ofpoor coverage.GUI ValueRange:MAP_HSUPA_TTI_2MS_SWITCH,MAP_INTER_RAT_PS_IN_CHANLE_LIMIT_SWITCH,MAP_PS_BE_ON_E_FACH_SWITCH,MAP_PS_STREAM_ON_E_FACH_SWITCH,MAP_PS_STREAM_ON_HSDPA_SWITCH,MAP_PS_STREAM_ON_HS



207



UPA_SWITCH,MAP_SRB_6800_WHEN_RAB_ON_HSDSCH_SWITCH,MAP_SRB_ON_DCH_OR_FACH_CS_RRC_SWITCH,MAP_CSPS_TTI_2MS_LIMIT_SWITCH,MAP_CSPS_PS_UL_USE_DCH_SWITCH,MAP_CSPS_PS_DL_USE_DCH_SWITCH,MAP_CSPS_MC_LIMIT_SWITCH,MAP_CSPS_RL_RESET_0K_LIMIT_SWITCHUnit:NoneActual ValueRange:MAP_HSUPA_TTI_2MS_SWITCH,MAP_INTER_RAT_PS_IN_CHANLE_LIMIT_SWITCH,MAP_PS_BE_ON_E_FACH_SWITCH,MAP_PS_STREAM_ON_E_FACH_SWITCH,MAP_PS_STREAM_ON_HSDPA_SWITCH,MAP_PS_STREAM_ON_HSUPA_SWITCH,



208



MAP_SRB_6800_WHEN_RAB_ON_HSDSCH_SWITCH,MAP_SRB_ON_DCH_OR_FACH_CS_RRC_SWITCH,MAP_CSPS_TTI_2MS_LIMIT_SWITCH,MAP_CSPS_PS_UL_USE_DCH_SWITCH,MAP_CSPS_PS_DL_USE_DCH_SWITCH,MAP_CSPS_MC_LIMIT_SWITCH,MAP_CSPS_RL_RESET_0K_LIMIT_SWITCHDefaultValue:MAP_HSUPA_TTI_2MS_SWITCH:0,MAP_INTER_RAT_PS_IN_CHANLE_LIMIT_SWITCH:0,MAP_PS_BE_ON_E_FACH_SWITCH:0,MAP_PS_STREAM_ON_E_FACH_SWITCH:0,MAP_PS_STREAM_ON_HSDPA_SWITCH:0,MAP_PS_STREAM_ON_HSUPA_SWITCH:0,MAP_SRB_6800_WHEN_R



209



AB_ON_HSDSCH_SWITCH:0,MAP_SRB_ON_DCH_OR_FACH_CS_RRC_SWITCH:1,MAP_CSPS_TTI_2MS_LIMIT_SWITCH:0,MAP_CSPS_PS_UL_USE_DCH_SWITCH:1,MAP_CSPS_PS_DL_USE_DCH_SWITCH:0,MAP_CSPS_MC_LIMIT_SWITCH:0,MAP_CSPS_RL_RESET_0K_LIMIT_SWITCH:0



210



CELLSCALEIND


ADDULOCELLMODULOCELLLST ULOCELL

WRFD-150201WRFD-151209

Macro & MicroCo-carrierUplinkInterferenceControlMacro-MicroDC-HSDPA

Meaning:Indi-cates whetherthe cell isconfigured as amacro cell ormicro cell. It isrecommendedthat themaximumtransmit powerof a cell be usedas a criterion forCellScaleInd.For example,cells with theirmaximumtransmit powerof less than 10 ware configuredas a micro cell.Otherwise, cellsare configuredas macro cells.In actualscenarios, thecriterion forCellScaleInd ischanged asrequired.GUI ValueRange:MACRO(Macro Cell),MICRO(MicroCell)Unit:NoneActual ValueRange:MACRO, MICRODefaultValue:MACRO(Macro Cell)



211

9 Counters

Table 9-1 Counter description

Counter ID Counter Name CounterDescription

NE Feature ID Feature Name

50331719 VS.HSDPA.DCCfg.AnchorCar-rierActedNum

Number of timesthat all the usersconfigured inDC mode in acell arescheduled byAnchorCarrierduring themeasurementperiod

NodeB Multi-mode:None

GSM: None

UMTS:WRFD-010610

WRFD-010689

WRFD-010696

LTE: None

HSDPAIntroductionPackageHSPA+Downlink42Mbps perUserDC-HSDPA

50331720 VS.HSDPA.DCCfg.SupCarrier-ActedNum

Total number oftimes DC-HSDPA-enabled usersare scheduled bythesupplementarycarrier

NodeB Multi-mode:NoneGSM: NoneUMTS:WRFD-010610WRFD-010689WRFD-010696LTE: None


50331721 VS.HSDPA.DCCfg.DualCarrierActedNum

Total number oftimes DC-HSDPA-enabled usersare scheduled bythe anchor andsupplementarycarriers at thesame time



WCDMA RANDC-HSDPA Feature Parameter Description 9 Counters


212



50332170 VS.DataOutput.DCHSDPA.Traffic

MAC-ehs trafficvolume of DC-HSDPA/DC-HSDPA+MIMO users

NodeB Multi-mode:NoneGSM: NoneUMTS:WRFD-150208WRFD-010699LTE: None

Flexible DualCarrier HSDPADC-HSDPA+MIMO

50332215 VS.DCHSDPA.DataTtiNum.User

Total number ofuser-level TTIswithin whichthere is data totransmit in DC-HSDPA/DC-HSDPA+MIMO userqueue buffers

NodeB Multi-mode:NoneGSM: NoneUMTS:WRFD-010696LTE: None

DC-HSDPA

50341702 VS.HSDPA.DCCfg.SupCarrierDeact.TimeRatio

The Ratio Of DcDeact


DB-HSDPATraffic-BasedActivation andDeactivation oftheSupplementaryCarrier In Multi-carrierDC-HSDPA+MIMO

73403828 VS.HSDPA.RAB.DC.AttEstab

Number of DC-HSDPA RABSetup Requestsin the primarycarrier of DC-HSDPA countedfor cell

BSC6900 WRFD-010696 DC-HSDPA

73403829 VS.HSDPA.RAB.DC.SuccEstab

Number of DC-HSDPA RABsSetupSuccessfully inthe primarycarrier of DC-HSDPA countedfor cell




213



73403830 VS.HSDPA.RAB.AbnormRel.DC

Number of DC-HSDPA RABsAbnormalReleased in theprimary carrierof DC countedfor Cell(including RFCause)


73403831 VS.HSDPA.RAB.NormRel.DC

Number of DC-HSDPA RABsNormalReleased in theprimary carrierof DC countedfor Cell


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

Average numberof DC-HSDPAUEs in anchorcarrier in a Cell


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

Average numberof DC-HSDPAUEs insupplementarycarrier in a Cell


73423377 VS.HSDPA.UE.Max.CAT25.28

MaximumNumber ofHSDPA UEswith Category25-28 in a Cell

BSC6900 WRFD-010699 DC-HSDPA+MIMO

73423378 VS.HSDPA.RAB.DCMIMO.AttEstab

Number of DC-HSDPA+MIMO RABSetup Requestsin the PrimaryCarrier of DC-HSDPA for Cell




214



73423379 VS.HSDPA.RAB.DCMIMO.SuccEstab

Number ofSuccessful DC-HSDPA+MIMO RABSetups in thePrimary Carrierof DC-HSDPAfor cell


73423380 VS.HSDPA.RAB.DCMIMO.NormRel

Number ofNormal DC-HSDPA+MIMO RABReleases in thePrimary Carrierof DC-HSDPAfor cell


73423381 VS.HSDPA.RAB.DCMIMO.AbnormRel

Number ofAbnormal DC-HSDPA+MIMO RABReleases in thePrimary Carrierof DC-HSDPAfor cell


73425890 VS.HSDPA.MC.SEC.UE.Mean.Cell

AverageNumber of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEsUsing This Cellas the SecondaryCarrier Cell

BSC6900 WRFD-150250WRFD-150207WRFD-150209WRFD-010696WRFD-150208WRFD-010699WRFD-150227WRFD-150223

3C-HSDPA4C-HSDPADB-HSDPADC-HSDPAFlexible DualCarrier HSDPADC-HSDPA+MIMODB-HSDPA+MIMOMC-HSDPA+MIMO



215



73425896 VS.HSDPA.MC.MeanRequiredPwr

Power Requiredby 4C-HSDPA/DB-HSDPA/DC-HSDPAUEs for Cell



73425901 VS.HSDPA.MC.MaxRequiredPwr

MaximumPower Requiredby 4C-HSDPA/DB-HSDPA/DC-HSDPAUEs for Cell



73425903 VS.HSDPA.MC.MinRequiredPwr

MinimumPower Requiredby 4C-HSDPA/DB-HSDPA/DC-HSDPAUEs for Cell





216



73425905 VS.MeanTCP.HSDPA.MC

Average DLTransmit Powerof 4C-HSDPA/DB-HSDPA/DC-HSDPAUEs for Cell



73425910 VS.MaxTCP.HSDPA.MC

Maximum DLTransmit Powerof 4C-HSDPA/DB-HSDPA/DC-HSDPAUEs for Cell



73425912 VS.MinTCP.HSDPA.MC

Minimum DLTransmit Powerof 4C-HSDPA/DB-HSDPA/DC-HSDPAUEs for Cell





217



73425928 VS.HSDPA.RAB.AbnormRel.DC2P

Number ofAbnormal RABReleases forCell DuringState Transitionof DC-HSDPAUEs to CELL/URA_PCH


73425931 VS.HSDPA.RAB.AbnormRel.DCMIMO2P

Number ofAbnormal RABReleases forCell DuringState Transitionof DC-HSDPA+MIMO UEs toCELL/URA_PCH


73425939 VS.HSDPA.RAB.NormRel.DC.All

Number ofNormal RABReleases of DC-HSDPA UEs forCell (AllScenarios)


73425942 VS.HSDPA.RAB.NormRel.DCMIMO.All

Number ofNormal RABReleases of DC-HSDPA+MIMO UEs forCell (AllScenarios)


73425958 RRC.SuccConnEstab.HSDSCH.AllCAT

Number ofSuccessful RRCConnectionSetups for Cell(Including Allthe HS-DSCHPhysical LayerCategories)

BSC6900 WRFD-01061002WRFD-010699WRFD-150207WRFD-150223

HSDPA UECategory 1 to 28

DC-HSDPA+MIMO

4C-HSDPA

MC-HSDPA+MIMO



218



73425964 RRC.SuccConnEstab.HSDSCH.CAT25.28

Number ofSuccessful RRCConnectionSetups for Cell(Including theHS-DSCHPhysical LayerCategories 25Through 28)


73441138 VS.HSDPA.UE.Mean.CAT25.28

AverageNumber ofHSDPA UEswith Category25-28 in a Cell


73403828 VS.HSDPA.RAB.DC.AttEstab

Number of DC-HSDPA RABSetup Requestsin the primarycarrier of DC-HSDPA countedfor cell


73403829 VS.HSDPA.RAB.DC.SuccEstab

Number of DC-HSDPA RABsSetupSuccessfully inthe primarycarrier of DC-HSDPA countedfor cell


73403830 VS.HSDPA.RAB.AbnormRel.DC

Number of DC-HSDPA RABsAbnormalReleased in theprimary carrierof DC countedfor Cell(including RFCause)




219



73403831 VS.HSDPA.RAB.NormRel.DC

Number of DC-HSDPA RABsNormalReleased in theprimary carrierof DC countedfor Cell


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

Average numberof DC-HSDPAUEs in anchorcarrier in a Cell


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

Average numberof DC-HSDPAUEs insupplementarycarrier in a Cell


73423377 VS.HSDPA.UE.Max.CAT25.28

MaximumNumber ofHSDPA UEswith Category25-28 in a Cell


73423378 VS.HSDPA.RAB.DCMIMO.AttEstab

Number of DC-HSDPA+MIMO RABSetup Requestsin the PrimaryCarrier of DC-HSDPA for Cell


73423379 VS.HSDPA.RAB.DCMIMO.SuccEstab

Number ofSuccessful DC-HSDPA+MIMO RABSetups in thePrimary Carrierof DC-HSDPAfor cell


73423380 VS.HSDPA.RAB.DCMIMO.NormRel

Number ofNormal DC-HSDPA+MIMO RABReleases in thePrimary Carrierof DC-HSDPAfor cell




220



73423381 VS.HSDPA.RAB.DCMIMO.AbnormRel

Number ofAbnormal DC-HSDPA+MIMO RABReleases in thePrimary Carrierof DC-HSDPAfor cell


73425890 VS.HSDPA.MC.SEC.UE.Mean.Cell

AverageNumber of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEsUsing This Cellas the SecondaryCarrier Cell



73425896 VS.HSDPA.MC.MeanRequiredPwr

Power Requiredby 4C-HSDPA/DB-HSDPA/DC-HSDPAUEs for Cell





221



73425901 VS.HSDPA.MC.MaxRequiredPwr

MaximumPower Requiredby 4C-HSDPA/DB-HSDPA/DC-HSDPAUEs for Cell



73425903 VS.HSDPA.MC.MinRequiredPwr

MinimumPower Requiredby 4C-HSDPA/DB-HSDPA/DC-HSDPAUEs for Cell



73425905 VS.MeanTCP.HSDPA.MC

Average DLTransmit Powerof 4C-HSDPA/DB-HSDPA/DC-HSDPAUEs for Cell





222



73425910 VS.MaxTCP.HSDPA.MC

Maximum DLTransmit Powerof 4C-HSDPA/DB-HSDPA/DC-HSDPAUEs for Cell



73425912 VS.MinTCP.HSDPA.MC

Minimum DLTransmit Powerof 4C-HSDPA/DB-HSDPA/DC-HSDPAUEs for Cell



73425928 VS.HSDPA.RAB.AbnormRel.DC2P

Number ofAbnormal RABReleases forCell DuringState Transitionof DC-HSDPAUEs to CELL/URA_PCH


73425931 VS.HSDPA.RAB.AbnormRel.DCMIMO2P

Number ofAbnormal RABReleases forCell DuringState Transitionof DC-HSDPA+MIMO UEs toCELL/URA_PCH




223



73425939 VS.HSDPA.RAB.NormRel.DC.All

Number ofNormal RABReleases of DC-HSDPA UEs forCell (AllScenarios)


73425942 VS.HSDPA.RAB.NormRel.DCMIMO.All

Number ofNormal RABReleases of DC-HSDPA+MIMO UEs forCell (AllScenarios)


73425958 RRC.SuccConnEstab.HSDSCH.AllCAT

Number ofSuccessful RRCConnectionSetups for Cell(Including Allthe HS-DSCHPhysical LayerCategories)

BSC6910 WRFD-01061002WRFD-010699WRFD-150207WRFD-150223

HSDPA UECategory 1 to 28

DC-HSDPA+MIMO

4C-HSDPA

MC-HSDPA+MIMO

73425964 RRC.SuccConnEstab.HSDSCH.CAT25.28

Number ofSuccessful RRCConnectionSetups for Cell(Including theHS-DSCHPhysical LayerCategories 25Through 28)


73441138 VS.HSDPA.UE.Mean.CAT25.28

AverageNumber ofHSDPA UEswith Category25-28 in a Cell




224

10 Glossary

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

WCDMA RANDC-HSDPA Feature Parameter Description 10 Glossary


225

11 Reference Documents

1. 3GPP TS 25.331, "Radio Resource Control (RRC)"2. 3GPP TS 25.306, "UE Radio Access capabilities"3. 3GPP TS 25.214, "Physical layer procedures (FDD)"4. HSDPA Feature Parameter Description5. Radio Bearers Feature Parameter Description6. Load Control Feature Parameter Description7. Directed Retry Decision Feature Parameter Description8. Handover Feature Parameter Description9. Green BTS Feature Parameter Description

WCDMA RANDC-HSDPA Feature Parameter Description 11 Reference Documents


226

dc-hsdpa(ran16.0 draft a)

Documents

huawei trademarks

huawei proprietary

huawei industrial basebantian

thepurchase scope

usage scope

dchsdpa cells

secondary cells

multicarrier cell groups