CE Efficiency Improvement for HSUPA TTI 2ms

Contents
7.4.4 CE Efficiency Improvement for HSUPA TTI 2ms

WCDMA RAN
CE Efficiency Improvement for HSUPA
TTI 2ms Feature Parameter Description
Issue 03
Date 2016-04-28

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2016. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and
recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any
kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Huawei Industrial Base Bantian, Longgang
Address:
Shenzhen 518129 People's Republic of China

Website: http://www.huawei.com
 Email: support@huawei.com

7.4.4 Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History
1.4 Differences Between Base Station Types

2 Overview
2.1 Background
2.2 Introduction
2.3 Benefits

3 Technical Description
3.1 Principles
3.2 Feature Impacts
3.2.1 Dynamic CE Resource Management
3.2.2 Admission CE Consumption for HSUPA UEs with a 2 ms TTI

4 Related Features

5 Network Impact

6 Engineering Guidelines
6.1 When to Use CE Efficiency Improvement for HSUPA TTI 2ms
6.2 Required Information
6.3 Deployment
6.3.1 Requirements
6.3.2 Data Preparation
6.3.3 Activation
6.3.4 Activation Observation
6.3.5 Deactivation
6.4 Performance Monitoring
6.5 Parameter Optimization
6.6 Troubleshooting

7 Parameters

8 Counters

9 Glossary

10 Reference Documents
1 About This Document

1.1 Scope

This document describes WRFD-160205 CE Efficiency Improvement for HSUPA TTI 2ms,
including the technical principles, related features, network impact, and engineering guidelines.
This document applies to the following NE types.

NE Type NE Model

RNC BSC6900, BSC6910

NodeB Macro 3900 series macro base stations: BTS3900, BTS3900A,

BTS3900L, BTS3900AL, DBS3900, BTS3900C

Micro Not supported

LampSite DBS3900 LampSite

1.2 Intended Audience

This document is intended for personnel who:

Need to understand the features described herein
Work with Huawei products

1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
Feature change
Changes in features of a specific product version
Editorial change
Changes in wording or addition of information that was not described in the earlier version

RAN16.0 03 (2016-04-28)

This issue includes the following changes.

 Change Type Change Description Parameter Change

Feature change Added the CE consumption rules on None

the WBBPf and UBBPd boards. For
details, see the following sections:
2.2 Introduction
3.1 Principles
3.2.2 Admission CE Consumption for HSUPA
UEs with a 2 ms TTI

Editorial None None

change

RAN16.0 02 (2016-02-29)

This issue includes the following changes.

Change Type Change Description Parameter Change

Feature change Modified the MML command Added the

configuration for activating this UlSRBTransModeOnHsupa(BSC6900
feature. For details, see the following ,BSC6910) parameter.
sections:
6.3.2 Data Preparation
6.3.3 Activation

Editorial None None

change

RAN16.0 01 (2014-04-30)

This issue includes the following changes.

Change Type Change Description Parameter Change

Feature change None None

Editorial Optimized the document description. None

change

RAN16.0 Draft B (2014-02-28)

This issue includes the following changes.

 Change Type Change Description Parameter Change

Feature change None None

Editorial change Added the descriptions about the None

feature and function differences
between NodeBs of different types.
For details, see section 1.4 Differences
Between Base Station Types.

RAN16.0 Draft A (2014-01-20)

This document is created for RAN16.0.

1.4 Differences Between Base Station Types

Feature Support by Macro, Micro, and LampSite Base Stations

Feature ID Description Supported by Supported Supported Supported

Controller(Y/N/NA) by by by
Macro(Y/N/ Micro(Y/N/ LampSite(Y
BSC6900 BSC6910 NA) NA) /N/NA)

WRFD- CE Yes Yes Yes No Yes

160205 Efficiency
Improveme
nt for
HSUPA TTI
2ms

NOTE:
NA indicates that an NE is not involved, that is, a feature does not require the support of the NE.

2 Overview

2.1 Background

Channel element (CE) resources are a type of NodeB resource. The number of CEs supported by
a NodeB is determined by the capabilities of its baseband boards. Downlink CEs are used for
encoding, spreading, and modulation. Uplink CEs are used for demodulation and decoding.
 CE resources are crucial for HSUPA UEs with a 2 ms transmission time interval (TTI) to
experience high rates and short service delays. An HSUPA UE with a 2 ms TTI consumes much
more uplink CE resources than an HSUPA UE with a 10 ms TTI. If CE resources are insufficient,
HSUPA UEs with a 2 ms TTI cannot access the network unless they use a 10 ms TTI.
CE resource usage is somewhat low on live networks. This is because the traffic model has been
changed as a result of the increasingly high penetration rates of smartphones and as a
consequence, an increased number of online HSUPA users. Although the data rate of these users
is low (at around 20 kbit/s), they still consume a considerable amount of CE resources.
To improve CE efficiency and adapt to the reality of today's traffic models, Huawei introduces
the WRFD-160205 CE Efficiency Improvement for HSUPA TTI 2ms feature.

2.2 Introduction

This feature improves CE efficiency for HSUPA UEs with a 2 ms TTI. With this feature, an
HSUPA UE consumes a minimum of one CE to maintain online and transmit data at a minimum
uplink rate of 20 kbit/s.

NOTE:
In two-antenna scenarios, the WBBPf board or UBBPd board will consume one CE. In four-antenna scenarios,
whilst the CE consumption for the UBBPd board is the same as that in two-antenna scenarios, the WBBPf board
will consume two CEs rather than one.

2.3 Benefits

This feature provides the following benefits when CE resources are insufficient:
Allows more HSUPA UEs with a 2 ms TTI to be admitted.
Increases the uplink throughput.

3 Technical Description

3.1 Principles

With CE Efficiency Improvement for HSUPA TTI 2ms, an HSUPA UE with a 2 ms TTI uses a
single HARQ process to transmit one RLC PDU with a default size of 40 bytes in each TTI. To
implement this, the NodeB sends an absolute grant (AG) message to deactivate the other seven
HARQ processes.
Figure 3-1 shows the technical principles.
 Figure 3-1 Technical principles of CE Efficiency Improvement for HSUPA TTI 2ms

shows the CE resources consumed in each TTI before this feature is enabled. The active
Figure 3-2
HARQ process uses spreading factor (SF) 4 and consumes eight CEs, while each of the other
inactive HARQ process consumes one CE. The average number of CEs consumed by a HARQ
process is 1.875.
Figure 3-2 CE consumption before this feature is enabled

After this feature is enabled, each HARQ process (active or inactive) consumes only one CE, as
shown in Figure 3-3.
Figure 3-3 CE consumption after this feature is enabled

NOTE:
The previous CE consumption rules apply only to two-antenna scenarios. In four-antenna scenarios, the CE
consumption rule on the UBBPd board is the same as that in two-antenna scenarios. However, on the WBBPf
board, two CEs are consumed for a UE using the single HARQ process.
CE consumption of UEs not using the single HARQ process depends on the requirement of the SF used by
each TTI. For more information about how to calculate CE consumption for such UEs, see CE Resource
Management Feature Parameter Description.

To enable this feature, run the NodeB MML command SET NODEBALGPARA with
CEIMPROVEMENT2MSSW set to ON(ON).

3.2 Feature Impacts

CE Efficiency Improvement for HSUPA TTI 2ms affects dynamic CE scheduling and CE
admission algorithm as follows:
 In dynamic CE scheduling, the scheduler can configure HSUPA UEs with a 2 ms TTI to
use a single HARQ process to transmit one RLC PDU in each TTI when uplink data rate
required by the UEs is 20 kbit/s or lower, thereby reducing CE consumption.
Each HSUPA UE with a 2 ms TTI consumes only one admission CE.

3.2.1 Dynamic CE Resource Management

The dynamic CE algorithm allocates CE resources to each HSUPA UE based on available CE

resources, UE's data transmission requirements, and user differentiation. When CE resources are
sufficient, more CEs are allocated to UEs that require rate upgrade. If CE resources become
insufficient, a rate downgrade is performed. To ensure that a UE is online, the downgraded rate
must not be lower than 160 kbit/s, which is the minimum requirement when a UE uses all the
eight active HARQ processes to transmit one RLC PDU. When CE Efficiency Improvement for
HSUPA TTI 2ms is enabled, the minimum rate of an HSUPA UE with a 2 ms TTI at the RLC
layer can be reduced from 160 kbit/s to 20 kbit/s, as such a UE can use a single HARQ process
to transmit one RLC PDU in each TTI.
CE Efficiency Improvement for HSUPA TTI 2ms also increases the differentiation between high-
priority and low-priority UEs when CE resources are insufficient. High-priority HSUPA UEs
with a 2 ms TTI can enjoy a maximum rate of 5.44 Mbit/s at the RLC layer. Therefore, the rate
differentiation ratio between high-priority and low-priority UEs is increased from 34:1
(5440:160) to 272:1 (5440/20).
shows dynamic CE resource management when CE Efficiency Improvement for
Figure 3-4
HSUPA TTI 2ms is enabled. For detailed description about dynamic CE resource management,
see HSUPA Feature Parameter Description. For information about CE consumption for a 2-ms-TTI
HSUPA service, see Table 3-4 and Table 3-6 in CE Resource Management Feature Parameter Description.
Figure 3-4 Dynamic CE resource management when CE Efficiency Improvement for HSUPA TTI 2ms is enabled

In addition to CE resource congestion scenarios, you can also enable a UE to use a single HARQ
process by setting the InitSingleHARQSW parameter to ON in the SET NODEBALGPARA
command when the CE Efficiency Improvement for HSUPA TTI 2ms is enabled. After the
switch is enabled, the NodeB sends a scheduling grant to all newly admitted HSUPA UEs with a
2 ms TTI so that they use a single HARQ process to transmit one RLC PDU in each TTI at 20
kbit/s. When CE resources are sufficient, the NodeB allows UEs that require higher data rates to
use all the eight HARQ processes to transmit data. The NodeB learns that a UE requires higher
data rate when the happy bit of the UE transmitted on the E-DCH Dedicated Physical Control
Channel (E-DPCCH) is "unhappy" and the value of Total E-DCH Buffer Status (TEBS) in the
Segmentation Indication (SI) field is larger than or equal to 20 kbit/s. The UE then uses all the
eight HARQ processes to transmit data even though it no longer requires such a high rate. This
situation lasts until the CE resources become insufficient and the NodeB instructs the UE to use a
single HARQ process to transmit the data.
This initial single HARQ function is recommended for NodeBs with insufficient CE resources
and a large number of UEs that require a low data rate (20 kbit/s). Using this function restricts
the instantaneous rate of UEs and therefore increases the uplink delay.
If the SrbChlTypeRrcEffectFlag(BSC6900,BSC6910) parameter is set to TRUE, the SRB over
E-DCH switch takes effect during an RRC connection establishment and the initial single HARQ
function does not take effect during a RAB setup.

3.2.2 Admission CE Consumption for HSUPA UEs with a 2 ms TTI

Table 3-1 describes admission CE consumption for HSUPA UEs with a 2 ms TTI.
 In versions earlier than RAN10.0, dynamic CE resource allocation is not supported and
admission CE resources for HSUPA UEs are calculated based on the maximum bit rate
(MBR). Each 2 ms TTI HSUPA UE consumes eight or more CEs.
For information about the WRFD-010638 Dynamic CE Resource Management feature,
see HSUPA Feature Parameter Description.
For information about the WRFD-140212 CE Overbooking feature, see CE Overbooking
Feature Parameter Description.

After the CE Efficiency Improvement for HSUPA TTI 2ms feature introduced in
RAN16.0 is enabled, one CE suffices for continuous data transmission by a 2 ms TTI
HSUPA UE. Therefore, only one CE is required for the 2 ms TTI HSUPA UE.
Table 3-1 Admission CE consumption

Feature Version Number of Required Admission

CEs

CE Consumption Calculated Based RAN10.0 and 8

on earlier
versions

Dynamic CE Resource Management RAN10.0 8

CE Overbooking RAN14.0 2-8

CE Efficiency Improvement for RAN16.0 1

HSUPA TTI 2ms

CE Efficiency Improvement for HSUPA TTI 2ms requires CE Overbooking, which allows the
NodeB to calculate consumed admission CE resources of admitted UEs and report the results to
the RNC through the common measurement report. The RNC then performs admission-CE-
based call access control (CAC), load reshuffling (LDR), and TTI switching.
Only the WBBPf and UBBPd boards support CE Efficiency Improvement for HSUPA TTI 2ms.
An uplink resource group may include WBBPf and UBBPd boards that support this feature and
others boards that do not. In sites enabled with this feature, only some of the 2 ms TTI UEs can
have services established on the WBBPf and UBBPd boards, whereas other 2 ms TTI UEs have
services established on the other boards. Admission CE consumption is calculated, respectively,
for these two types of UEs as follows:
For 2 ms TTI HSUPA UEs with services established on the WBBPf and UBBPd boards, a
UE consumes one CE only in two-antenna scenarios as what a 10 ms TTI UE does. In four-
antenna scenarios, the CE consumption rule on the UBBPd board is the same as that in two-
antenna scenarios. However, on the WBBPf board, two CEs are consumed for a UE using
the single HARQ process. Therefore, they will not be switched to use a 10 ms TTI when CE
resources are insufficient. The NodeB informs the RNC that these UEs do not support
admission-CE-based or CE-consumption-based TTI adjustments using the private fields in
 the RL Setup Response, RL Reconfiguration Response Ready, or RL Add Response
messages.
For 2 ms TTI HSUPA UEs with service established on other boards, admission CE
consumption is calculated based on the actual UE data rate, minimum number of CEs
reserved for 2 ms TTI UEs enabled with CE Overbooking, data rate required by the
guaranteed bit rate (GBR) and for transmitting one RLC PDU. Consequently, these UEs
will be switched to use a 10 ms TTI when CE resources are insufficient.

4 Related Features

Prerequisite Features

Feature ID Feature Name Description

WRFD-010638 Dynamic CE Resource N/A

Management

WRFD-140212 CE Overbooking

Mutually Exclusive Features

None

Impacted Features

Feature ID Feature Name Description

WRFD-010695 UL Layer 2 When UL Layer 2 Improvement is enabled, the

Improvement active HARQ process of a UE can use SF8 at
most and the minimum RLC rate can be further
reduced to 15 kbit/s.

N/A Admission-CE-based When admission-CE-based dynamic TTI

dynamic TTI adjustment for a single BE service over HSUPA is
adjustment for a single enabled,
BE service over HSUPA UEs with a 2 ms TTI with services
HSUPA established on the WBBPf or UBBPd board
cannot be switched to use a 10 ms TTI if
uplink CE resources become insufficient.
HSUPA UEs with a 10 ms TTI with services
 Feature ID Feature Name Description

established on the WBBPf or UBBPd board

can be switched to use a 2 ms TTI if uplink
CE resources become insufficient.
For HSUPA UEs with a 2 ms TTI and newly
admitted UEs whose services are established
on the WBBPf or UBBPd board, 2 ms-to-10
ms TTI switching is not performed if uplink CE
resources become insufficient.
The reason is as follows:
The minimum RLC rate for 10 ms TTI HSUPA UEs
is 32 kbit/s. If the CE Efficiency Improvement for
HSUPA TTI 2ms feature is disabled, the minimum
RLC rate for 2 ms TTI HSUPA UEs is 160 kbit/s.
Therefore, when CEs are limited, TTI needs to be
changed from 2 ms to 10 ms to decrease CE
consumption. After the CE Efficiency Improvement
for HSUPA TTI 2ms feature is enabled, HSUPA
UEs with a 2 ms TTI can transmit data by using
only one CE, which is the same as that for HSUPA
UEs with a 10 ms TTI. As a result, a 2 ms-to-10
ms TTI switching is not required when uplink CE
resources are insufficient.
For details about the function for admission CE-
based dynamic TTI adjustment of BE services, see
HSUPA TTI Selection Feature Parameter Description.

WRFD-010686 CPC-DTX/DRX When both the CE Efficiency Improvement for

HSUPA TTI 2ms and CPC features are enabled,
ensure that both the values of cycle1 and cycle2
configured for CPC UEs are 8 or multiples of 8, so
as to keep the single HARQ function compatible
with the DTX function. If the parameters
configured for CPC UEs do not meet certain
conditions, the UTRAN will automatically identify
CPC UEs, and configure cycle1 as 8 and cycle2
as 16. This function is introduced in RNC running
R16SPC630 and NodeB running R16SPC180,
before when CPC UEs do not support the single
HARQ function.

5 Network Impact
System Capacity

Increased number of HSUPA UEs with a 2 ms TTI

When compared with CE Overbooking, this feature further increases the number of HSUPA
UEs with a 2 ms TTI that need to continuously transmit a large amount of data by two to
eight times when CE resources are insufficient.
Higher HSUPA cell throughput
If you enable HSUPA UEs with a 2 ms TTI requiring a low data rate to use a single HARQ
process from the beginning to transmit data in a cell loaded normally, UEs with data transfer
requirements can use more CE resources, which increases the uplink throughput. The
increased throughput depends on the number of HSUPA UEs with a 2 ms TTI requiring a
low data rate and the number of such UEs that use a single HARQ process to transmit data.

Network Performance

When compared with CE Overbooking, this feature further decreases the amount of admission
CE resources consumed by HSUPA UEs with a 2 ms TTI since they only use one admission CE.
The admission CE consumption for such UEs can now be precisely evaluated based on the
number of UEs on the live network. With CE Overbooking, admission CE consumption for UEs
with a 10 ms TTI can be precisely evaluated based on the rate required for transmitting one RLC
PDU. CE resources for R99 UEs are assigned and consumed in a fixed manner.
If the uplink CE resources are insufficient and admission-CE-based dynamic TTI adjustment is
not enabled, this feature allows more UEs to be admitted, increasing the cell access success rate.
When this feature is enabled together with admission-CE-based and CE-consumption-based
dynamic TTI adjustment, if CE resources become insufficient, 2ms-to-10ms TTI switching is not
performed on HSUPA UEs with a 2 ms TTI. As a result, a single cell serves more HSUPA UEs
with 2 ms TTIs and the number of times TTI switching is triggered decreases.
When this feature is enabled, the number of times HSUPA UEs experience service drops due to
poor coverage may increase because a 2 ms TTI provides weaker coverage than a 10 ms TTI.
You are advised to enable coverage-based dynamic TTI adjustment to prevent this situation from
occurring.
When compared with an HSUPA UE with a 2 ms TTI that uses all the eight HARQ processes to
transmit data, an HSUPA UE with a 2 ms TTI that uses a single HARQ process has a lower peak
rate. Therefore, the service delay of such UEs may be prolonged.

6 Engineering Guidelines

6.1 When to Use CE Efficiency Improvement for HSUPA TTI 2ms

 This feature is recommended for NodeBs where,
HSUPA UEs that support a 2 ms TTI account for more than 60% of all HSUPA UEs.
Admission CE congestion still occurs after the CE Overbooking feature is enabled.
Access requests initiated by UEs with a 2 ms TTI are denied or these UEs are
switched to use a 10 ms TTI.
Consumed CE resources account for 70% of all configured CE resources for the
NodeB.

6.2 Required Information

You must collect the values of the following counters.

Collect the values of the following counters on the RNC:
VS.HSUPA.UE.Mean.CAT1.4(BSC6900,BSC6910): Average Number of HSUPA
UEs with Category 1-4 in a Cell
VS.HSUPA.UE.Mean.CAT5(BSC6900,BSC6910)~VS.HSUPA.UE.Mean.CAT9(B
SC6900,BSC6910): Average Number of HSUPA UEs with Category 5 in a Cell~Average
Number of HSUPA UEs with Category 9 in a Cell
HSUPA UEs that support a 2 ms TTI account for more than 60% of all HSUPA UEs in a
NodeB if the following inequality is true:
(VS.HSUPA.UE.Mean.CAT6(BSC6900,BSC6910)~9)/
(VS.HSUPA.UE.Mean.CAT1.4(BSC6900,BSC6910)+
(VS.HSUPA.UE.Mean.CAT5(BSC6900,BSC6910)~9) 60%
Collect the values of the following counters on the RNC. If any of the following counters
has a value other than 0, access denial caused by insufficient admission CE resources
occurred in the NodeB.
VS.RRC.Rej.ULCE.Cong(BSC6900,BSC6910): Number of RRC Connection
Rejects for Cell (UL CE Resource Congestion)
VS.RAB.FailEstabCS.ULCE.Cong(BSC6900,BSC6910): Number of Failed CS
RAB Establishments for Cell (UL CE Congestion)
VS.RAB.FailEstabPS.ULCE.Cong(BSC6900,BSC6910): Number of Failed PS
RAB Establishments for Cell (UL CE Congestion)
VS.HSUPA.RAB.FailEstab.ULCE.Cong(BSC6900,BSC6910): Number of Failed
HSUPA Service Establishments Due to UL CE Insufficiency for Cell
Collect the values of the following counters on the RNC. If either of the following
counters has a value other than 0, 2ms-to-10ms TTI switching caused by insufficient
admission CE resources occurred in the NodeB.
 VS.HSUPA.TTI2to10.ADMCE.Succ(BSC6900,BSC6910): Number of Successful
TTI Switchovers Based on Admitted CEs During RB Reconfiguration in a Cell(2ms to
10ms)
VS.HSUPA.RABEstabTTI10ms.AdmCE.Succ(BSC6900,BSC6910): Number of
Successful RAB Establishments Initiated by HSUPA 2ms UEs with a 10 ms TTI Due
to Congestion of Admitted CEs in a Cell
Collect the values of the following counters on the RNC and NodeB:
VS.NodeB.ULCreditUsed.Mean(BSC6900,BSC6910): Average NodeB Uplink
Credit Usage When CE Overbooking Is Enabled for NodeB (RNC)
VS.LC.ULCreditUsed.Mean(BSC6900,BSC6910): Mean Usage of UL Credit for
Cell (RNC)
VS.LC.ULCreditAvailable.Shared: Number of UL CEs configured for a shared group
(NodeB)
If CE Overbooking is enabled, admission-CE congestion is about to occur if the following
inequality is true:
(VS.NodeB.ULCreditUsed.Mean(BSC6900,BSC6910)/2)/VS.LC.ULCreditAvailable.Shared
70%
If CE Overbooking is not enabled, admission-CE congestion is about to occur if the
following inequality is true:
(VS.LC.ULCreditUsed.Mean(BSC6900,BSC6910)/2)/VS.LC.ULCreditAvailable.Shared 70%

6.3 Deployment

6.3.1 Requirements

Other Features

See "4 Related Features" in Impacted Features.

Hardware

The 3900 series base stations must be configured with the WBBPf or UBBPd board. The
WBBPa board must not be contained in any downlink resource groups within a NodeB.
You can run the NodeB MML command LST BASEBANDEQM to check the baseband boards
included in the downlink resource groups and run the NodeB MML command DSP
BRDMFRINFO to query the type of a baseband board.

License

For details about how to activate the license, see License Management Feature Parameter Description.
 If RAN Sharing or MOCN is enabled, the licensed value is allocated among the primary and
secondary operators according to the value of the "License Allocation for Multiple Operators"
parameter.

Feature ID Feature License License Lice NE License Sale

Name Control Control nse Allocation s
Item Name Con for Unit
trol Multiple
Item Operators
Nam
e on
U20
00
GUI

WRFD- CE LQW9CEE CE HSU NodeB Method 1 per

160205 Efficiency FF01 Efficiency PA Nod
Improveme Improveme 2ms eB
nt for nt for TTI
HSUPA TTI HSUPA TTI CE
2ms 2ms (per effici
NodeB) ency
Enha
nced
(per
Nod
eB)

Method 1: Some license control items, for example, Dynamic CE Function (per NodeB), can be
allocated only through the common group. For NodeB license allocation among multiple
operators, see License Management Feature Parameter Description.

Others

The UE is of HSUPA category 6 or higher.

There are no non-scheduling services in the uplink.
The maximum size of an RLC PDU is 336 bits.

6.3.2 Data Preparation

Table 6-1 lists the data to prepare before activating CE Efficiency Improvement for HSUPA TTI
2ms.
Table 6-1 Data to prepare before activating CE Efficiency Improvement for HSUPA TTI 2ms
Parameter Name Parameter ID Setting Notes Data source Remarks

SRB transmission UlSRBTransMo Set this parameter to Engineering NE: RNC

mode on HSUPA deOnHsupa(BS SCHEDULED. design
 Parameter Name Parameter ID Setting Notes Data source Remarks

C6900,BSC6910) MO: UFRC

Batch
modification
on the CME
is
supported.

HSUPA 2ms CE CEIMPROVEMENT Set this parameter to Engineering NE: NodeB

Efficiency 2MSSW ON(ON). design MO:
Improvement NODEBAL
Switch GPARA
Batch
modification
on the CME
is
supported.

6.3.3 Activation

Using MML Commands

1. Run the RNC MML command SET UFRC with SRB transmission mode on HSUPA
set to SCHEDULED.
2. Run the NodeB MML command SET NODEBALGPARA with HSUPA 2ms CE
Efficiency Improvement Switch set to ON(ON).

MML Command Examples

//Setting SRB transmission mode on HSUPA to SCHEDULED

SET UFRC: ULSRBTRANSMODEONHSUPA=SCHEDULED;
//Activating CE Efficiency Improvement for HSUPA TTI 2ms
SET NODEBALGPARA: CEIMPROVEMENT2MSSW=ON;

Using the CME

Based on the parameter configurations involved in 6.3.2 Data Preparation, perform the following
operations to activate this feature:

NOTE:
When configuring the feature on the CME, perform a single configuration first, and then perform a batch
modification if required.
Configure the parameters of a single object before a batch modification. Perform a batch modification before
logging out of the parameter setting interface.
 1. Configure a single object (such as a cell) on the CME.
Set parameters listed in the table in "Data Preparation" section from top to bottom on the
CME. For instructions on how to perform the CME single configuration, see CME Single
Configuration Operation Guide.

2. (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects in batches, click on the CME to start the batch modification wizard.
For instructions on how to perform a batch modification through the CME batch
modification center, press F1 while running the wizard to obtain online help.
To check whether a parameter supports batch modification, see the Remarks column in the
table in "Data Preparation" section.

6.3.4 Activation Observation

Check the value of the NodeB counter VS.HSUPA.AlltoSingleHARQNum.CECong, which indicates the
number of times an HSUPA UE with a 2 ms TTI stops using all eight HARQ processes and starts
to use a single HARQ process to transmit data due to insufficient CE resources. If the counter
value is not 0, CE Efficiency Improvement for HSUPA TTI 2ms has been activated.
You can also run the DSP ULOCELL command to check whether the feature has been enabled.

6.3.5 Deactivation

The following table describes the parameters for deactivating this feature.

Parameter Parameter ID Setting Notes Remarks

Name

HSUPA 2ms CE CEIMPROVEMENT2MS Set this NE: NodeB

Efficiency SW parameter to MO: NODEBALGPARA
Improvement OFF(OFF). Batch modification on the CME
Switch is supported.

Using MML Commands

Run the NodeB MML command SET NODEBALGPARA with HSUPA 2ms CE Efficiency
Improvement Switch set to OFF(OFF).

MML Command Examples

//Deactivating CE Efficiency Improvement for HSUPA TTI 2ms

SET NODEBALGPARA: CEIMPROVEMENT2MSSW=OFF;

Using the CME

The method of feature deactivation using the CME is the same as that of feature activation using
the CME. For detailed operations, see Using the CME.
6.4 Performance Monitoring

With this feature activated, admission CE consumption is expected to decrease. You can observe
the counters listed in the following two tables.
Counters related to consumed admission CEs within a NodeB

Counter Name Counter Description

VS.NodeB.ULCreditUsed.Mean(BS Average NodeB Uplink Credit Usage When CE

C6900,BSC6910) Overbooking Is Enabled for NodeB

VS.NodeB.ULCreditUsed.Max(BSC Maximum NodeB Uplink Credit Usage When CE

6900,BSC6910) Overbooking Is Enabled for NodeB

Counters related to CE resource usage of a local cell group (LCG)

Counter Name Counter Description

VS.LCG.ULCreditUsage.Mean(BSC Average Uplink Credit Usage of LCG for Cell

6900,BSC6910)

VS.LCG.ULCreditUsage.Max(BSC69 Maximum Uplink Credit Usage of LCG for Cell

00,BSC6910)

With this feature activated, the number of UEs in the CELL_DCH state, HSUPA UEs, and UEs
with a 2 ms TTI is expected to increase. You can observe the counters listed in the following
table.
Counter related to the number of UEs in the CELL_DCH state, HSUPA UEs, and UEs
with a 2 ms TTI

Counter Name Counter Description

VS.CellDCHUEs(BSC6900,BSC6910) Number of UEs in CELL_DCH State for Cell

VS.HSUPA.UE.Max.cell(BSC6900,BSC691 Maximum Number of HSUPA UEs in a Cell

0)

VS.HSUPA.UE.Mean.cell(BSC6900,BSC6 Average Number of HSUPA UEs in a Cell

910)

VS.HSUPA.UE.Max.TTI2ms(BSC6900,BS Maximum Number of HSUPA 2 ms TTI UEs in a

C6910) Cell

VS.HSUPA.UE.Mean.TTI2ms(BSC6900,B Average Number of HSUPA 2 ms TTI UEs in a Cell

SC6910)
With this feature activated, the number of failed RRC/RAB setup attempts and the number of
times TTI switching and LDR are triggered due to insufficient CE resources are expected to
decrease. You can observe the counters listed in the following three tables.
Counters related to the number of failed RRC/RAB setup attempts caused by insufficient
uplink CE resources

Counter Name Counter Description

VS.RRC.Rej.ULCE.Cong(BSC6900,BSC6 Number of RRC Connection Rejects for Cell (UL

910) CE Resource Congestion)

VS.RAB.FailEstabCS.ULCE.Cong(BSC Number of Failed CS RAB Establishments for Cell

6900,BSC6910) (UL CE Congestion)

VS.RAB.FailEstabPS.ULCE.Cong(BSC6 Number of Failed PS RAB Establishments for Cell

900,BSC6910) (UL CE Congestion)

VS.HSUPA.RAB.FailEstab.ULCE.Cong Number of Failed HSUPA Service Establishments

(BSC6900,BSC6910) Due to UL CE Insufficiency for Cell

Counters related to the number of times TTI switching is triggered due to insufficient CE
resources

Counter Name Counter Description

VS.HSUPA.TTI2to10.ADMCE.Succ(BSC Number of Successful TTI Switchovers Based on

6900,BSC6910) Admitted CEs During RB Reconfiguration in a
Cell(2ms to 10ms)

VS.HSUPA.RABEstabTTI10ms.AdmCE Number of Successful RAB Establishments Initiated

.Succ(BSC6900,BSC6910) by HSUPA 2 ms UEs with a 10 ms TTI Due to
Congestion of Admitted CEs in a Cell

Counter related to the number of times LDR is triggered due to insufficient CE resources

Counter Name Counter Description

VS.LCC.LDR.Num.ULCE(BSC6900,BSC6 Number of Times a Cell Is in LDR State Due to UL

910) CE Resource Congestion for Cell

With this feature activated, the number of times HSUPA UEs experience service drops due to
insufficient CE resources is expected to decrease. However, the number of times HSUPA UEs
experience service drops due to poor coverage will increase because 2 ms TTI provides weaker
coverage than 10 ms TTI. You can observe the counters listed in the following table.
Counters related to HSUPA service drops
 Counter Name Counter Description

VS.HSUPA.RAB.AbnormRel(BSC69 Number of HSUPA RABs Abnormal Releases for Cell

00,BSC6910)

VS.HSUPA.RAB.AbnormRel.E2P(B Number of RABs Abnormally Released for PS HSUPA

SC6900,BSC6910) Services during the State Transition from CELL_DCH to
CELL_PCH or URA_PCH for Cell

VS.HSUPA.RAB.NormRel(BSC6900, Number of HSUPA RABs Normal Released for Cell

BSC6910)

VS.HSUPA.HHO.E2D.SuccOutIntra Number of Successful HSUPA Intra-Frequency Hard

Freq(BSC6900,BSC6910) Handovers for Cell(EDCH to DCH)

VS.HSUPA.E2F.Succ(BSC6900,BSC69 Number of Successful Channel Conversions from

10) EDCH to FACH for HSUPA Service for Cell

VS.HSUPA.E2D.Succ(BSC6900,BSC6 Number of Successful Channel Conversions from

910) EDCH to DCH for HSUPA Service for Cell

VS.HSUPA.E2P.Succ(BSC6900,BSC6 Number of Successful Times That a UE Performing

910) HSUPA Services Transits to CELL_PCH or URA_PCH
State for cell

With this feature activated, network load may raise due to the increased number of UEs with a 2
ms TTI. You can observe the counters listed in the following two tables.
Counter related to the cell average RTWP

Counter Name Counter Description

VS.MeanRTWP(BSC6900,BSC69 Mean Power of Totally Received Bandwidth for Cell

10)

Counters related to air interface load of a cell (NodeB)

Counter Name Counter Description

VS.HSUPA.LoadOutput.0 through Number of Cell Ul Load Between 0db to

VS.HSUPA.LoadOutput.25 0.5db through Number of Cell Ul Load
above 30db

With this feature activated, uplink HSUPA throughput in the case of insufficient CE resources
may increase. However, if cell load is heavy, uplink HSUPA throughput may decrease because 2
ms TTI results in more loads than 10 ms TTI. You can observe the counters listed in the
following table.
 Counters related to average HSUPA throughput within in a cell (NodeB)

Counter Name Counter Description

VS.HSUPA.Thruput.ROTAll/(SP*60) Average throughput of HSUPA users in a cell

VS.HSUPA.Thruput.ROTAll/ Average throughput of HSUPA users in a cell

(VS.HSUPA.DataTtiNum*0.002) when data is transmitted

With this feature activated, you can check CE consumption and number of HSUPA UEs with a 2
ms TTI transmitting data at a low rate by observing the counters listed in the following two
tables.
Counters related to CE consumption on the NodeB (NodeB)

Counter Name Counter Description

VS.ULCE.Mean.Shared Average Shared Uplink CE

VS.LC.ULMean.LicenseGroup.Shared Average number of UL CEs consumed in a shared

group

VS.CE.ULMean.UlGroup Mean Number of Uplink CEs Consumed by All Cells in

an Uplink Resource Group

Counter related to the number of HSUPA UEs with a 2 ms TTI transmitting data at a low
rate

Counter Name Counter Description

VS.HSUPA.LowRateTTI2msUserNumber Average number of 2 ms TTI HSUPA users at a rate

lower than or equal to 23.25 kbit/s in a cell

After this feature is activated, you can check the number of times an HSUPA UE with a 2 ms TTI
stops using all the eight HARQ processes and begins to use a single HARQ process to transmit
data due to insufficient CE resources and vice versa by observing the counters listed in the
following table.
Counters related to the number of times an HSUPA UE with a 2 ms TTI stops using all
the eight HARQ processes and starts to use a single HARQ process to transmit data due to
insufficient CE resources and vice versa (NodeB)

Counter Name Counter Description

VS.HSUPA.AlltoSingleHARQNum.CECong Number of transitions from using all HARQ

processes to using a single HARQ process due to
limited CEs in the cell
 Counter Name Counter Description

VS.HSUPA.SingletoAllHARQNum Number of Transitions from Using A Single HARQ

Process to Using All HARQ Processes In the Cell

Number of failed RRC/RAB setup attempts caused by insufficient downlink CE

resources

Counter Name Counter Description

VS.RRC.Rej.DLCE.Cong(BSC6900,BSC6 Number of RRC Connection Rejects for Cell (DL CE

910) Resource Congestion)

VS.RAB.FailEstabCS.DLCE.Cong(BSC Number of Failed CS RAB Establishments for Cell

6900,BSC6910) (DL CE Congestion)

VS.RAB.FailEstabPS.DLCE.Cong(BSC Number of Failed PS RAB Establishments for Cell

6900,BSC6910) (DL CE Congestion)

6.5 Parameter Optimization

With this feature activated, if the number of times service drops occur due to poor coverage
increases, you are advised to enable coverage-based dynamic TTI adjustment. For detailed
operations, see HSUPA TTI Selection Feature Parameter Description.
As the air-interface efficiency of UEs with a 2 ms TTI is lower than that of UEs with a 10 ms
TTI, cell load may increase after this feature is activated. As a result, congestion increases in
heavily loaded cells, leading to reduced uplink throughput, rejected uplink power admissions, or
call drops. To combat this effect, you are advised to enable Turbo IC Phase2. For detailed
operations, see HSUPA Data Channel Interference Cancellation Feature Parameter Description. You can also
enable TTI switching based on the RTWP to switch UEs from the 2 ms TTI or the 10 ms TTI
when the uplink load is heavy.
When this feature is enabled, if the consumed CE resources accounts for 60% of all configured
CE resources for the NodeB and there are more than 10 HSUPA UEs with a 2 ms TTI requiring a
low data rate (indicated by the VS.HSUPA.LowRateTTI2msUserNumber counter), you can enable such
UEs to use an initial single HARQ process to save CE resources. However, this will prolong
service delay. Therefore, you are not advised to do so unless the actual CE usage still exceeds
60% of the congestion threshold after the feature is activated.
Once this feature is activated, if the number of denied access attempts caused by insufficient
downlink CE resources increases, run the NodeB MML command SET
NODEBRESALLOCRULE with Resource Allocate Rule set to CAPAFIRST(Capacity First
Rule).

6.6 Troubleshooting

None
7 Parameters

Table 7-1 Parameters

Param NE MML Featur Featur Description
eter ID Comm e ID e
and Name

UlSRBTr BSC69 SET WRFD- SRB Meaning: Data transmission mode for the 2
ansMode 00 UFRC 010636 over ms TTI E-DCH carrying SRBs. This parameter
OnHsupa
HSUPA takes effect only when 2 ms TTI E-DCH
carries SRBs.
GUI Value Range: SCHEDULED, NON-
SCHEDULED
Unit: None
Actual Value Range: SCHEDULED, NON-
SCHEDULED
Default Value: SCHEDULED

UlSRBTr BSC69 SET WRFD- SRB Meaning: Data transmission mode for the 2
ansMode 10 UFRC 010636 over ms TTI E-DCH carrying SRBs. This parameter
OnHsupa
HSUPA takes effect only when 2 ms TTI E-DCH
carries SRBs.
GUI Value Range: SCHEDULED, NON-
SCHEDULED
Unit: None
Actual Value Range: SCHEDULED, NON-
SCHEDULED
Default Value: SCHEDULED

CEIMPR BTS39 SET WRFD- CE Meaning: Indicates the switch for CE

OVEMEN 00, NODEBA 160205 Efficien efficiency improvement for 2 ms TTI HSUPA
T2MSSW LGPARA
BTS39 cy users.
LST
00 NODEBA Improv GUI Value Range: OFF(OFF), ON(ON)
WCDM LGPARA ement Unit: None
A for
HSUPA Actual Value Range: OFF, ON
TTI Default Value: OFF(OFF)
2ms

INITSING BTS39 SET WRFD- CE Meaning: Indicates the switch for initial
LEHARQ 00, NODEBA 160205 Efficien activation of single HARQ for 2 ms TTI
SW LGPARA
BTS39 cy HSUPA users. If this switch is turned on,
LST
Param NE MML Featur Featur Description
eter ID Comm e ID e
and Name

00 NODEBA Improv single HARQ takes effect on newly admitted

WCDM LGPARA ement users.
A for GUI Value Range: OFF(OFF), ON(ON)
HSUPA Unit: None
TTI
2ms Actual Value Range: OFF, ON
Default Value: OFF(OFF)

SrbChlTy BSC69 SET WRFD- 3.4/6.8/ Meaning: Whether the configured type of the
peRrcEff 00 UFRCCH 010510 13.6/27 channel that preferably carries the uplink
ectFlag LTYPEPA
RA WRFD- .2Kbps signaling RB is effective in the case of RRC
010611 RRC connection establishment. If this parameter is
12 Connec set to TRUE, the uplink SRB can be
WRFD- tion and configured on the E-DCH at the RRC
150232 Radio connection setup phase when
Access [UFRCCHLTYPEPARA:SrbChlType] is set to
WRFD- Bearer HSUPA or HSPA. If this parameter is set to
010652 Establis FALSE, the uplink SRB cannot be configured
hment on the E-DCH at the RRC connection setup
and phase.
Releas GUI Value Range: FALSE, TRUE
e Unit: None
HSDPA Actual Value Range: TRUE, FALSE
DRD
Default Value: False
Multiba
nd
Direct
Retry
Based
on UE
Locatio
n
SRB
over
HSDPA

SrbChlTy BSC69 SET WRFD- 3.4/6.8/ Meaning: Whether the configured type of the
peRrcEff 10 UFRCCH 010510 13.6/27 channel that preferably carries the uplink
ectFlag LTYPEPA
RA WRFD- .2Kbps signaling RB is effective in the case of RRC
010611 RRC connection establishment. If this parameter is
12 Connec set to TRUE, the uplink SRB can be
WRFD- tion and configured on the E-DCH at the RRC
150232 Radio connection setup phase when
Access [UFRCCHLTYPEPARA:SrbChlType] is set to
WRFD- Bearer HSUPA or HSPA. If this parameter is set to
010652
Param NE MML Featur Featur Description
eter ID Comm e ID e
and Name

Establis FALSE, the uplink SRB cannot be configured

hment on the E-DCH at the RRC connection setup
and phase.
Releas GUI Value Range: FALSE, TRUE
e Unit: None
HSDPA Actual Value Range: TRUE, FALSE
DRD
Default Value: False
Multiba
nd
Direct
Retry
Based
on UE
Locatio
n
SRB
over
HSDPA

8 Counters

Table 8-1 Counters

Counter ID Counter Counter NE Feature ID Feature
Name Description Name

50331850 VS.HSUPA.Load Number of NodeB Multi-mode: HSUPA

Output.0 Cell Ul Load None Introduction
Between 0db GSM: None Package
to 0.5db UMTS:
WRFD-
010612
LTE: None

50331875 VS.HSUPA.Load Number of NodeB Multi-mode: HSUPA

Output.25 Cell Ul Load None Introduction
above 30db GSM: None Package
UMTS:
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

WRFD-
010612
LTE: None

50331879 VS.HSUPA.Data Number of NodeB Multi-mode: HSUPA

TtiNum TTIs in which None Introduction
HSUPA users GSM: None Package
transmit data UMTS:
in a cell WRFD-
010612
LTE: None

50331958 VS.HSUPA.Allto Number of NodeB Multi-mode: CE Efficiency

SingleHARQNum transitions None Improvement
.CECong
from using all GSM: None for HSUPA
HARQ UMTS: TTI 2ms
processes to WRFD-
using a single 160205
HARQ
LTE: None
process due
to limited CEs
in the cell

50331959 VS.HSUPA.Singl Number of NodeB Multi-mode: Turbo IC

etoAllHARQNum Transitions None Phase 2
from Using A GSM: None CE Efficiency
Single HARQ UMTS: Improvement
Process to WRFD- for HSUPA
Using All 160213 TTI 2ms
HARQ
WRFD-
Processes In
the Cell 160205
LTE: None

50332550 VS.ULCE.Mean. Average NodeB Multi-mode: RAN Sharing

Shared Shared Uplink None Introduction
CE GSM: None Package
UMTS:
WRFD-
021304
LTE: None

50332559 VS.LC.ULCreditA Number of UL NodeB Multi-mode: Admission

vailable.Shared CEs None Control
configured for GSM: None
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

a shared UMTS:
group WRFD-
020101
LTE: None

50332561 VS.LC.ULMean.L Average NodeB Multi-mode: Admission

icenseGroup.Sha number of UL None Control
red
CEs GSM: None
consumed in UMTS:
an shared WRFD-
group 020101
LTE: None

50332574 VS.CE.ULMean. Mean Number NodeB Multi-mode: Admission

UlGroup of Uplink CEs None Control
Consumed by GSM: None
All Cells in an UMTS:
Uplink WRFD-
Resource 020101
Group
LTE: None

50341883 VS.HSUPA.Thru Cell NodeB Multi-mode: HSUPA

put.ROTAll throughput of None Introduction
HSUPA users GSM: None Package
under all UMTS:
uplink Uu WRFD-
loads 010612
LTE: None

50341892 VS.HSUPA.LowR Average NodeB Multi-mode: CE Efficiency

ateTTI2msUserN number of 2 None Improvement
umber
ms TTI GSM: None for HSUPA
HSUPA users UMTS: TTI 2ms
at a rate lower WRFD-
than or equal 160205
to 23.25 kbit/s
in a cell LTE: None

67190404 VS.RRC.Rej.UL Number of BSC6900 WRFD- Admission

CE.Cong RRC 020101 Control
Connection WRFD- 3.4/6.8/13.6/2
Rejects for 010510 7.2Kbps RRC
Cell (UL CE Connection
Resource and Radio
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

Congestion) Access
Bearer
Establishment
and Release

67190404 VS.RRC.Rej.UL Number of BSC6910 WRFD- Admission

CE.Cong RRC 020101 Control
Connection WRFD- 3.4/6.8/13.6/2
Rejects for 010510 7.2Kbps RRC
Cell (UL CE Connection
Resource and Radio
Congestion) Access
Bearer
Establishment
and Release

67190405 VS.RRC.Rej.DL Number of BSC6900 WRFD- Admission

CE.Cong RRC 020101 Control
Connection WRFD- 3.4/6.8/13.6/2
Rejects for 010510 7.2Kbps RRC
Cell (DL CE Connection
Resource and Radio
Congestion) Access
Bearer
Establishment
and Release

67190405 VS.RRC.Rej.DL Number of BSC6910 WRFD- Admission

CE.Cong RRC 020101 Control
Connection WRFD- 3.4/6.8/13.6/2
Rejects for 010510 7.2Kbps RRC
Cell (DL CE Connection
Resource and Radio
Congestion) Access
Bearer
Establishment
and Release

67190406 VS.RAB.FailEsta Number of BSC6900 WRFD- Admission

bCS.ULCE.Cong Failed CS 020101 Control
RAB WRFD- 3.4/6.8/13.6/2
Establishment 010510 7.2Kbps RRC
s for Cell (UL Connection
CE and Radio
Congestion) Access
Bearer
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

Establishment
and Release

67190406 VS.RAB.FailEsta Number of BSC6910 WRFD- Admission

bCS.ULCE.Cong Failed CS 020101 Control
RAB WRFD- 3.4/6.8/13.6/2
Establishment 010510 7.2Kbps RRC
s for Cell (UL Connection
CE and Radio
Congestion) Access
Bearer
Establishment
and Release

67190407 VS.RAB.FailEsta Number of BSC6900 WRFD- Admission

bCS.DLCE.Cong Failed CS 020101 Control
RAB WRFD- 3.4/6.8/13.6/2
Establishment 010510 7.2Kbps RRC
s for Cell (DL Connection
CE and Radio
Congestion) Access
Bearer
Establishment
and Release

67190407 VS.RAB.FailEsta Number of BSC6910 WRFD- Admission

bCS.DLCE.Cong Failed CS 020101 Control
RAB WRFD- 3.4/6.8/13.6/2
Establishment 010510 7.2Kbps RRC
s for Cell (DL Connection
CE and Radio
Congestion) Access
Bearer
Establishment
and Release

67190408 VS.RAB.FailEsta Number of BSC6900 WRFD- Admission

bPS.ULCE.Cong Failed PS 020101 Control
RAB WRFD- 3.4/6.8/13.6/2
Establishment 010510 7.2Kbps RRC
s for Cell (UL Connection
CE and Radio
Congestion) Access
Bearer
Establishment
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

and Release

67190408 VS.RAB.FailEsta Number of BSC6910 WRFD- Admission

bPS.ULCE.Cong Failed PS 020101 Control
RAB WRFD- 3.4/6.8/13.6/2
Establishment 010510 7.2Kbps RRC
s for Cell (UL Connection
CE and Radio
Congestion) Access
Bearer
Establishment
and Release

67190409 VS.RAB.FailEsta Number of BSC6900 WRFD- Admission

bPS.DLCE.Cong Failed PS 020101 Control
RAB WRFD- 3.4/6.8/13.6/2
Establishment 010510 7.2Kbps RRC
s for Cell (DL Connection
CE and Radio
Congestion) Access
Bearer
Establishment
and Release

67190409 VS.RAB.FailEsta Number of BSC6910 WRFD- Admission

bPS.DLCE.Cong Failed PS 020101 Control
RAB WRFD- 3.4/6.8/13.6/2
Establishment 010510 7.2Kbps RRC
s for Cell (DL Connection
CE and Radio
Congestion) Access
Bearer
Establishment
and Release

67192364 VS.HSUPA.RAB. Number of BSC6900 WRFD- Interactive

AbnormRel HSUPA RABs 01061206 and
Abnormal WRFD- Background
Releases for 010632 Traffic Class
Cell on HSUPA
Streaming
Traffic Class
on HSUPA

67192364 VS.HSUPA.RAB. Number of BSC6910 WRFD- Interactive

AbnormRel
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

HSUPA RABs 01061206 and

Abnormal WRFD- Background
Releases for 010632 Traffic Class
Cell on HSUPA
Streaming
Traffic Class
on HSUPA

67192365 VS.HSUPA.RAB. Number of BSC6900 WRFD- Interactive

NormRel HSUPA RABs 01061206 and
Normal WRFD- Background
Released for 010632 Traffic Class
Cell on HSUPA
Streaming
Traffic Class
on HSUPA

67192365 VS.HSUPA.RAB. Number of BSC6910 WRFD- Interactive

NormRel HSUPA RABs 01061206 and
Normal WRFD- Background
Released for 010632 Traffic Class
Cell on HSUPA
Streaming
Traffic Class
on HSUPA

67192470 VS.HSUPA.E2D. Number of BSC6900 WRFD- HSUPA

Succ Successful 01061208 DCCC
Channel
Conversions
from EDCH to
DCH for
HSUPA
Service for
Cell

67192470 VS.HSUPA.E2D. Number of BSC6910 WRFD- HSUPA

Succ Successful 01061208 DCCC
Channel
Conversions
from EDCH to
DCH for
HSUPA
Service for
Cell
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

67192472 VS.HSUPA.HHO. Number of BSC6900 WRFD- HSUPA

E2D.SuccOutIntr Successful 01061204 Mobility
aFreq
HSUPA Intra- Management
Frequency
Hard
Handovers for
Cell(EDCH to
DCH)

67192472 VS.HSUPA.HHO. Number of BSC6910 WRFD- HSUPA

E2D.SuccOutIntr Successful 01061204 Mobility
aFreq
HSUPA Intra- Management
Frequency
Hard
Handovers for
Cell(EDCH to
DCH)

67192481 VS.HSUPA.E2F. Number of BSC6900 WRFD- HSUPA

Succ Successful 01061208 DCCC
Channel
Conversions
from EDCH to
FACH for
HSUPA
Service for
Cell

67192481 VS.HSUPA.E2F. Number of BSC6910 WRFD- HSUPA

Succ Successful 01061208 DCCC
Channel
Conversions
from EDCH to
FACH for
HSUPA
Service for
Cell

67192640 VS.LCC.LDR.Nu Number of BSC6900 WRFD- Load

m.ULCE Times a Cell 020106 Reshuffling
Is in LDR
State Due to
UL CE
Resource
Congestion
for Cell
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

67192640 VS.LCC.LDR.Nu Number of BSC6910 WRFD- Load

m.ULCE Times a Cell 020106 Reshuffling
Is in LDR
State Due to
UL CE
Resource
Congestion
for Cell

67199617 VS.MeanRTWP Mean Power BSC6900 WRFD- Load

of Totally 020102 Measurement
Received
Bandwidth for
Cell

67199617 VS.MeanRTWP Mean Power BSC6910 WRFD- Load

of Totally 020102 Measurement
Received
Bandwidth for
Cell

67202567 VS.LC.ULCredit Mean Usage BSC6900 WRFD- Admission

Used.Mean of UL Credit 020101 Control
for Cell

67202567 VS.LC.ULCredit Mean Usage BSC6910 WRFD- Admission

Used.Mean of UL Credit 020101 Control
for Cell

67203850 VS.HSUPA.UE.M Average BSC6900 WRFD- 20 HSUPA

ean.Cell Number of 01061211 Users per Cell
HSUPA UEs WRFD- 60 HSUPA
in a Cell 010634 Users per Cell
WRFD- 96 HSUPA
010639 Users per Cell

67203850 VS.HSUPA.UE.M Average BSC6910 WRFD- 20 HSUPA

ean.Cell Number of 01061211 Users per Cell
HSUPA UEs WRFD- 60 HSUPA
in a Cell 010634 Users per Cell
WRFD- 96 HSUPA
010639 Users per Cell

67204266 VS.HSUPA.UE.M Average BSC6900 WRFD- HSUPA UE

ean.CAT1.4 Number of 01061201 Category
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

HSUPA UEs Support

with Category
1-4 in a Cell

67204266 VS.HSUPA.UE.M Average BSC6910 WRFD- HSUPA UE

ean.CAT1.4 Number of 01061201 Category
HSUPA UEs Support
with Category
1-4 in a Cell

67204267 VS.HSUPA.UE.M Average BSC6900 WRFD- HSUPA UE

ean.CAT5 Number of 01061201 Category
HSUPA UEs Support
with Category
5 in a Cell

67204267 VS.HSUPA.UE.M Average BSC6910 WRFD- HSUPA UE

ean.CAT5 Number of 01061201 Category
HSUPA UEs Support
with Category
5 in a Cell

67204268 VS.HSUPA.UE.M Average BSC6900 WRFD- HSUPA UE

ean.CAT6 Number of 01061201 Category
HSUPA UEs Support
with Category
6 in a Cell

67204268 VS.HSUPA.UE.M Average BSC6910 WRFD- HSUPA UE

ean.CAT6 Number of 01061201 Category
HSUPA UEs Support
with Category
6 in a Cell

73393834 VS.HSUPA.RAB. Number of BSC6900 WRFD- Interactive

FailEstab.ULCE. Failed HSUPA 01061206 and
Cong
Service WRFD- Background
Establishment 010632 Traffic Class
s Due to UL on HSUPA
CE Streaming
Insufficiency Traffic Class
for Cell on HSUPA

73393834 VS.HSUPA.RAB. Number of BSC6910 WRFD- Interactive

FailEstab.ULCE. Failed HSUPA 01061206 and
Cong
Service Background
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

Establishment WRFD- Traffic Class

s Due to UL 010632 on HSUPA
CE Streaming
Insufficiency Traffic Class
for Cell on HSUPA

73403761 VS.HSUPA.UE.M Maximum BSC6900 WRFD- HSUPA

ax.Cell Number of 01061202 Admission
HSUPA UEs WRFD- Control
in a Cell 020101 Admission
Control

73403761 VS.HSUPA.UE.M Maximum BSC6910 WRFD- HSUPA

ax.Cell Number of 01061202 Admission
HSUPA UEs WRFD- Control
in a Cell 020101 Admission
Control

73410510 VS.CellDCHUEs Number of BSC6900 WRFD- UE State in

UEs in 010202 Connected
CELL_DCH Mode (CELL-
State for Cell DCH, CELL-
PCH, URA-
PCH, CELL-
FACH)

73410510 VS.CellDCHUEs Number of BSC6910 WRFD- UE State in

UEs in 010202 Connected
CELL_DCH Mode (CELL-
State for Cell DCH, CELL-
PCH, URA-
PCH, CELL-
FACH)

73422163 VS.HSUPA.E2P. Number of BSC6900 WRFD- UE State in

Succ Successful 010202 Connected
Times That a Mode (CELL-
UE DCH, CELL-
Performing PCH, URA-
HSUPA PCH, CELL-
Services FACH)
Transits to
CELL_PCH or
URA_PCH
State for cell
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

73422163 VS.HSUPA.E2P. Number of BSC6910 WRFD- UE State in

Succ Successful 010202 Connected
Times That a Mode (CELL-
UE DCH, CELL-
Performing PCH, URA-
HSUPA PCH, CELL-
Services FACH)
Transits to
CELL_PCH or
URA_PCH
State for cell

73422168 VS.HSUPA.RAB. Number of BSC6900 WRFD- UE State in

AbnormRel.E2P RABs 010202 Connected
Abnormally WRFD- Mode (CELL-
Released for 010612 DCH, CELL-
PS HSUPA PCH, URA-
Services PCH, CELL-
during the FACH)
State HSUPA
Transition Introduction
from Package
CELL_DCH to
CELL_PCH or
URA_PCH for
Cell

73422168 VS.HSUPA.RAB. Number of BSC6910 WRFD- UE State in

AbnormRel.E2P RABs 010202 Connected
Abnormally WRFD- Mode (CELL-
Released for 010612 DCH, CELL-
PS HSUPA PCH, URA-
Services PCH, CELL-
during the FACH)
State HSUPA
Transition Introduction
from Package
CELL_DCH to
CELL_PCH or
URA_PCH for
Cell

73424007 VS.NodeB.ULCr Maximum BSC6900 WRFD- CE

editUsed.Max NodeB Uplink 140212 Overbooking
Credit Usage
When CE
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

Overbooking
Is Enabled for
NodeB

73424007 VS.NodeB.ULCr Maximum BSC6910 WRFD- CE

editUsed.Max NodeB Uplink 140212 Overbooking
Credit Usage
When CE
Overbooking
Is Enabled for
NodeB

73424199 VS.HSUPA.UE.M Maximum BSC6900 WRFD- HSUPA

ax.TTI2ms Number of 010612 Introduction
HSUPA 2 ms WRFD- Package
TTI UEs in a 01061403 HSUPA 2ms
Cell TTI

73424199 VS.HSUPA.UE.M Maximum BSC6910 WRFD- HSUPA

ax.TTI2ms Number of 010612 Introduction
HSUPA 2 ms WRFD- Package
TTI UEs in a 01061403 HSUPA 2ms
Cell TTI

73424205 VS.HSUPA.RAB Number of BSC6900 None None

EstabTTI10ms.A Successful
dmCE.Succ
RAB
Establishment
s Initiated by
HSUPA 2 ms
UEs with a 10
ms TTI Due to
Congestion of
Admitted CEs
in a Cell

73424205 VS.HSUPA.RAB Number of BSC6910 None None

EstabTTI10ms.A Successful
dmCE.Succ
RAB
Establishment
s Initiated by
HSUPA 2 ms
UEs with a 10
ms TTI Due to
Congestion of
Admitted CEs
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

in a Cell

73424209 VS.HSUPA.TTI2t Number of BSC6900 WRFD- HSUPA

o10.ADMCE.Suc Successful 01061404 2ms/10ms TTI
c
TTI Handover
Switchovers
Based on
Admitted CEs
During RB
Reconfigurati
on in a
Cell(2ms to
10ms)

73424209 VS.HSUPA.TTI2t Number of BSC6910 WRFD- HSUPA

o10.ADMCE.Suc Successful 01061404 2ms/10ms TTI
c
TTI Handover
Switchovers
Based on
Admitted CEs
During RB
Reconfigurati
on in a
Cell(2ms to
10ms)

73426283 VS.LCG.ULCredi Average BSC6900 WRFD- CE

tUsage.Mean Uplink Credit 140212 Overbooking
Usage of LCG
for Cell

73426283 VS.LCG.ULCredi Average BSC6910 WRFD- CE

tUsage.Mean Uplink Credit 140212 Overbooking
Usage of LCG
for Cell

73426284 VS.LCG.ULCredi Maximum BSC6900 WRFD- CE

tUsage.Max Uplink Credit 140212 Overbooking
Usage of LCG
for Cell

73426284 VS.LCG.ULCredi Maximum BSC6910 WRFD- CE

tUsage.Max Uplink Credit 140212 Overbooking
Usage of LCG
for Cell
Counter ID Counter Counter NE Feature ID Feature
Name Description Name

73441218 VS.NodeB.ULCr Average BSC6900 WRFD- CE

editUsed.Mean NodeB Uplink 140212 Overbooking
Credit Usage
When CE
Overbooking
Is Enabled for
NodeB

73441218 VS.NodeB.ULCr Average BSC6910 WRFD- CE

editUsed.Mean NodeB Uplink 140212 Overbooking
Credit Usage
When CE
Overbooking
Is Enabled for
NodeB

73441236 VS.HSUPA.UE.M Average BSC6900 WRFD- HSUPA UE

ean.CAT9 Number of 01061201 Category
HSUPA UEs Support
with Category
9 in a Cell

73441236 VS.HSUPA.UE.M Average BSC6910 WRFD- HSUPA UE

ean.CAT9 Number of 01061201 Category
HSUPA UEs Support
with Category
9 in a Cell

73441239 VS.HSUPA.UE.M Average BSC6900 WRFD- HSUPA

ean.TTI2ms Number of 010612 Introduction
HSUPA 2 ms WRFD- Package
TTI UEs in a 01061403 HSUPA 2ms
Cell TTI

73441239 VS.HSUPA.UE.M Average BSC6910 WRFD- HSUPA

ean.TTI2ms Number of 010612 Introduction
HSUPA 2 ms WRFD- Package
TTI UEs in a 01061403 HSUPA 2ms
Cell TTI
9 Glossary

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

10 Reference Documents

1. 3GPP TS 25.211, " Physical channels and mapping of transport channels onto physical
channels (FDD)"
2. 3GPP TS 25.321, " Medium Access Control (MAC) protocol specification"
3. CE Resource Management Feature Parameter Description

4. CE Overbooking Feature Parameter Description

5. HSUPA Feature Parameter Description

6. HSUPA TTI Selection Feature Parameter Description

7. HSUPA Data Channel Interference Cancellation Feature Parameter Description

8. License Management Feature Parameter Description