Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
RAN14.0
Issue
04
Date
2013-05-10
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website:
http://www.huawei.com
Email:
support@huawei.com
WCDMA RAN
HSDPA
Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
Issue 04 (2013-05-10)
ii
WCDMA RAN
HSDPA
Contents
7 Network Impact..........................................................................................................................7-1
7.1 WRFD-010610 HSDPA Introduction Package .............................................................................. 7-1
7.1.1 System Capacity ................................................................................................................... 7-1
7.1.2 Network Performance ........................................................................................................... 7-1
7.2 WRFD-010653 96 HSDPA Users per Cell .................................................................................... 7-1
7.2.1 System Capacity ................................................................................................................... 7-1
7.2.2 Network Performance ........................................................................................................... 7-1
7.3 WRFD-010654 128 HSDPA Users per Cell .................................................................................. 7-1
7.3.1 System Capacity ................................................................................................................... 7-1
Issue 04 (2013-05-10)
iii
WCDMA RAN
HSDPA
Contents
Issue 04 (2013-05-10)
iv
WCDMA RAN
HSDPA
Contents
Issue 04 (2013-05-10)
WCDMA RAN
HSDPA
Contents
9 Parameters..................................................................................................................................9-1
10 Counters..................................................................................................................................10-1
11 Glossary ..................................................................................................................................11-1
12 Reference Documents .........................................................................................................12-1
Issue 04 (2013-05-10)
vi
WCDMA RAN
HSDPA
1 Introduction
1 Introduction
1.1 Scope
This document describes the HSDPA functional area. It provides an overview of the main functions and
goes into details regarding HSDPA control and user plane functions.
Editorial change: refers to the change in wording or the addition of the information that was not
described in the earlier version.
Document Issues
The document issues are as follows:
04 (2013-05-10)
03 (2012-11-30)
02 (2012-07-20)
01 (2012-04-30)
Draft A (2012-02-15)
04 (2013-05-10)
This is the document for the fourth commercial release of RAN14.0.
Compared with issue 03 (2012-11-30) of RAN14.0, this issue incorporates the changes described in the
following table.
Change Type
Change Description
Parameter Change
Feature change
None
None
Editorial
change
None
Issue 04 (2013-05-10)
1-1
WCDMA RAN
HSDPA
1 Introduction
BLER Target
6 Related Features
7 Network Impact
8 Engineering Guidelines
03 (2012-11-30)
This is the document for the third commercial release of RAN14.0.
Compared with issue 02 (2012-07-20) of RAN14.0, this issue incorporates the changes described in the
following table.
Change Type
Change Description
Feature change
Editorial
change
Parameter Change
None
None
02 (2012-07-20)
This is the document for the second commercial release of RAN14.0.
Compared with issue 01 (2012-04-30) of RAN14.0, this issue incorporates the changes described in the
following table.
Change Type
Change Description
Parameter Change
None
Editorial change Added the procedures for deploying features used in this None
document. For details, see 8 "Engineering Guidelines."
01 (2012-04-30)
This is the document for the first commercial release of RAN14.0.
Compared with issue Draft A (2012-02-15) of RAN14.0, this issue incorporates the changes described in
the following table.
Issue 04 (2013-05-10)
1-2
WCDMA RAN
HSDPA
Change Type
1 Introduction
Change Description
Parameter Change
None
None
Draft A (2012-02-15)
This is the first draft of the document for RAN14.0.
Compared with 03 (2011-10-30) of RAN13.0, this issue incorporates the following changes:
Change Type
Change Description
Feature change
Issue 04 (2013-05-10)
Parameter Change
None
1-3
WCDMA RAN
HSDPA
2 Overview of HSDPA
2 Overview of HSDPA
2.1 General Principles of HSDPA
To meet the rapidly growing demands for data services on the mobile network, 3GPP Release 5
introduced HSDPA in 2005. HSDPA improves the downlink capacity, increases the user data rate greatly,
and reduces the transmission delay on the WCDMA network.
The characteristics of HSDPA are as follows:
Fast scheduling
Fast scheduling introduced into the NodeB determines the UEs for data
transmission in each TTI (2 ms) and dynamically allocates resources to these
UEs. It improves the usage of system resources and increases the system
capacity.
For details about how Huawei RAN implements fast scheduling, see section4.3
"MAC-hs Scheduling."
Fast HARQ
Fast hybrid automatic repeat request (HARQ) is used to rapidly request the
retransmission of erroneously received data.
Specifically, when the UE detects an erroneous data transmission, it saves the
received data and requests the NodeB to retransmit the original data at the
physical layer. Before decoding, the UE performs soft combining of the saved data
and the retransmitted data. The combining fully uses the data transmitted each
time and therefore increases the decoding success rate. In addition, the
retransmission delay at the physical layer is reduced greatly, compared with that
at the RLC layer.
For details about how Huawei RAN implements fast HARQ, see section 4.4
"HARQ."
Fast AMC
The MAC-hs, a new MAC sublayer, is introduced into the UE and NodeB to support HSDPA.
Issue 04 (2013-05-10)
2-1
WCDMA RAN
HSDPA
2 Overview of HSDPA
2.2.2 HS-SCCH
HS-SCCH is a high-speed shared control channel. It carries the control information related to the
HS-PDSCH. The control information includes the UE identity, HARQ-related information, and information
about transport format and resource combination (TFRC). For each transmission of the HS-DSCH, one
HS-SCCH is required to carry the related control information. One cell can be configured with several
HS-SCCHs. The number of HS-SCCHs determines the maximum number of UEs that can be scheduled
simultaneously in each TTI.
2.2.3 HS-DPCCH
HS-DPCCH is a high speed dedicated physical control channel. In the uplink, each HSDPA UE must be
configured with an HS-DPCCH. This channel is mainly used by the UE to report the CQI and whether a
transport block is correctly received. The information about the transport block is used for fast
retransmission at the physical layer. The CQI is used for AMC and scheduling to allocate Uu resources.
Issue 04 (2013-05-10)
2-2
WCDMA RAN
HSDPA
2 Overview of HSDPA
The HSDPA UE must be configured with dedicated physical control channels in both the uplink and the
downlink.
The uplink DPCCH is used for closed-loop power control by working with the DPCH or F-DPCH. In
addition, the uplink DPCCH power is used as a reference for the HS-DPCCH power.
The downlink DPCH is used for inner-loop power control and as a reference for the HS-PDSCH power.
Like the downlink DPCH, the F-DPCH is also used for inner-loop power control. The difference is that
each UE must have a downlink DPCH (SF256) whereas 10 UEs can share an F-DPCH (SF256) to save
downlink channel codes.
Maximum Number
of HS-DSCH Codes
Minimum TTI
Maximum
Number of
Data Blocks
Maximum Data
Rate (Mbit/s)
7298
1.2
7298
1.2
7298
1.8
7298
1.8
7298
3.6
7298
3.6
10
14411
7.2
10
14411
7.2
15
20251
10.2
Issue 04 (2013-05-10)
2-3
WCDMA RAN
HSDPA
2 Overview of HSDPA
10
15
27952
14.4
11
3630
0.9
12
3630
1.8
Bearer mapping
The bearer mapping is used by the network side to configure the RAB during the setup of a service
connection in the cell. The network side then configures bearer channels for the UE based on the
requested service type, service rate, UE capability, and cell capability.
For details, see section 3.1 "Bearer Mapping."
Access control
Issue 04 (2013-05-10)
2-4
WCDMA RAN
HSDPA
2 Overview of HSDPA
Access control, a sub-function of load control, checks whether the current resources of the cell are
sufficient for the service connection setup. If the resources are insufficient, intelligent access control is
triggered. If the resources are sufficient, the service connection can be set up.
For details, see section 3.2 "Access Control."
Mobility management
For the established HS-DSCH connection, mobility management decides whether to switch it to
another cell for providing better services, based on the channel quality of the UE.
For details, see section 3.3 "Mobility Management."
Channel switching
Channel switching is responsible for switching the transport channel among the HS-DSCH, DCH, and
FACH based on the requirements of mobility management or load control.
For details, see section 3.4 "Channel Switching."
Load control
When the cell load increases, the load control function adjusts the resources configured for the
established radio connections to avoid cell overload.
For details, see section 3.5 "Load Control."
Resource management
Resource management coordinates the power resource between the HS-DSCH and the DCH and the
code resource between the HS-SCCH and the HS-PDSCH. The downlink power and codes are the
bottleneck resources of the cell. Resource management can increase the HSDPA capacity.
Power resource management reserves power for channels of different types and allocates power for
them. For details, see section 3.6 "Power Resource Management."
Code resource management allocates and reserves code resources for channels of different types. In
addition, it collects and reshuffles idle code resources.
For details, see section 3.7 "Code Resource Management."
Issue 04 (2013-05-10)
2-5
WCDMA RAN
HSDPA
2 Overview of HSDPA
The service data is passed to the RLC layer and MAC-d of the RNC for processing and encapsulation.
Then, the MAC-d PDU is formed and passed through the Iub/Iur interface to the NodeB/RNC. To avoid
congestion, the flow control and congestion control functions control the traffic on the Iub/Iur interface
through the HS-DSCH frame protocol (3GPP TS 25.435).
After the MAC-d PDU is received by the NodeB, it is passed through the MAC-hs to the physical layer
and then sent out through the Uu interface. The MAC-hs provides MAC-hs scheduling, TFRC selection,
and HARQ. MAC-hs scheduling determines the HSDPA users in the cell for data transmission. TFRC
selection determines the transmission rates and Uu resources to be allocated to the HSDPA UEs. HARQ
is used to implement the hybrid automatic repeat request function.
Issue 04 (2013-05-10)
2-6
WCDMA RAN
HSDPA
3 Control Plane
3 Control Plane
This chapter consists of the following sections:
Bearer Mapping
Access Control
Mobility Management
Channel Switching
Load Control
Service Type
Can Be Carried on
HS-DSCH?
Optional Feature?
Signaling (SRB)
Yes
Yes
Feature name: SRB over HSDPA
CS
Voice
Yes
Yes
Feature name: CS Voice over
HSPA/HSPA+
PS
Videophone
No
No
Streaming
No
No
Conversational
Yes
Yes
Feature name: VoIP over HSPA/HSPA+
Streaming
Yes
Yes
Feature name: Streaming Traffic Class on
HSDPA
Interactive
Yes
No
Background
Yes
No
IMS signaling
Yes
Yes
Feature name: IMS Signaling over HSPA
MBMS PTP
Yes
Yes
Feature name: MBMS P2P over HSDPA
During the service setup, the RNC selects appropriate channels based on the UE capability, cell
capability, and service parameters to optimize the use of cell resources and ensure the QoS. Huawei
RAN supports the setting of the types of RABs carried on the HS-DSCH according to service
requirements. For details, see Radio Bearers Feature Parameter Description.
Issue 04 (2013-05-10)
3-1
WCDMA RAN
HSDPA
3 Control Plane
Issue 04 (2013-05-10)
3-2
WCDMA RAN
HSDPA
3 Control Plane
Table 3-2 lists new state transition and new channel switching.
Table 3-2 New state transition and new channel switching
New State Transition
Here, the switching between HS-DSCH and FACH can be triggered by traffic volume, which is similar to
the switching between DCH and FACH. For details, see State Transition Feature Parameter Description.
In addition, when the cell load is too high, load control may also trigger the switching from the HS-DSCH
to the FACH to relieve congestion. For details, see Load Control Feature Parameter Description.
As the HS-DSCH is introduced later, it is inevitable that some cells support the HS-DSCH but others do
not. This is also the case with UEs. When a service is set up, the channel switching function selects an
appropriate bearer channel based on the cell capability and UE capability to ensure the QoS while
efficiently using the cell resources. When the user is moving, the channel switching function adjusts the
channel type based on the UE capability to ensure service continuity while improving user experience.
Issue 04 (2013-05-10)
3-3
WCDMA RAN
HSDPA
3 Control Plane
Triggers for switching from the HS-DSCH to the DCH are as follows:
The HS-DSCH is selected during the service setup but neither the resources of the serving cell nor the
resources of the inter-frequency same-coverage neighboring cell are sufficient. In this case, the
HS-DSCH is switched to the DCH. This function is achieved by means of non-periodic directed retry
decision (DRD). For details about non-periodic DRD, see Directed Retry Decision Feature Parameter
Description.
The HS-DSCH serving cell changes. The UE attempts to set up a new HS-DSCH connection with the
new best cell. In such a case, the possible scenarios are as follows:
If
the new best cell does not support the HS-DSCH, the UE cannot set up the HS-DSCH connection.
In this case, the HS-DSCH is switched to the DCH.
If
the new best cell supports the HS-DSCH but a new HS-DSCH connection cannot be set up
because the resources are insufficient, the DCH connection is set up and the HS-DSCH is switched
to this DCH.
For details, see Handover Feature Parameter Description.
The user moves from a cell supporting the DCH but not supporting the HS-DSCH to a cell supporting
the HS-DSCH. In this case, the DCH connection is also set up because the DCH supports soft
handover, which can increase the handover success rate.
In one of the cases described previously, the DCH connection is set up in a cell supporting the HS-DSCH
or in an inter-frequency same-coverage neighboring cell supporting the HS-DSCH. Then, the DCH is
switched to the HS-DSCH by either of the following mechanisms:
Issue 04 (2013-05-10)
3-4
WCDMA RAN
HSDPA
3 Control Plane
Every TTI, the NodeB detects the power usage of R99 channels to determine the power available for
HSPA. To reserve the power for R99 power control itself, the power margin PwrMgn needs to be set on
the NodeB side. In addition, the power allocated to HSPA must not exceed the maximum permissible
power HspaPower, which can be set on the RNC side.
Issue 04 (2013-05-10)
3-5
WCDMA RAN
HSDPA
3 Control Plane
For details on uplink HS-DPCCH power control, see Power Control Feature Parameter Description.
Issue 04 (2013-05-10)
3-6
WCDMA RAN
HSDPA
3 Control Plane
The
The
number of codes that can be shared between HS-PDSCH and DPCH is equal to the value of
HsPdschMaxCodeNum minus the value of HsPdschMinCodeNum, as shown in Figure 3-5. When
a code that can be shared is idle, it can be allocated to the HS-PDSCH if the idle code is adjacent to
the allocated HS-PDSCH codes.
Issue 04 (2013-05-10)
3-7
WCDMA RAN
HSDPA
3 Control Plane
The dynamic code allocation controlled by the NodeB is more flexible than the dynamic code allocation
controlled by the RNC. The dynamic code allocation controlled by the NodeB shortens the code
allocation duration and reduces the number of Iub signaling messages transmitted for code reallocation.
If NodeB-controlled dynamic code allocation is enabled, the RNC-controlled dynamic code allocation is
disabled dynamically.
Huawei recommends the following code allocation modes, where the first mode is preferred:
Configure the RNC to use static code allocation and the NodeB to use dynamic code allocation.
If the NodeB does not support dynamic code allocation, configure the RNC to use dynamic code
allocation.
If not all the NodeBs controlled by an RNC support dynamic code allocation, the RNC-controlled
dynamic code allocation is recommended. In this case, the NodeB-controlled dynamic code allocation
can also be enabled for those supporting NodeBs.
The cell is not in the basic congestion state that is triggered by code resource. For details about basic
congestion state, see Load Control Feature Parameter Description.
The switch parameter CodeAdjForHsdpaSwitch is set to ON. In this case, the RNC moves the codes
occupied by R99 users leftward along the code tree and thereby releases shared codes that are close
to HS-PDSCH codes. Figure 3-7 shows how this works.
When the RNC-controlled dynamic code allocation or the NodeB-Controlled Dynamic Code Allocation is
enabled, codes released by means of dynamic code tree reshuffling can be used by the HS-PDSCH to
improve throughput for HSDPA users.
Whether the F-DPCH codes can be reallocated through dynamic code tree reshuffling is determined by
the parameter RsvdPara1: RSVDBIT6 in the MML command ADD UCELLALGOSWITCH
When dynamic code tree reshuffling takes effect, the RNC reshuffles the codes used by the
DPCH/F-DPCH to provide more continuous SF16 codes for HSDPA through this function. This function
is described as follows:
Every time the codes used by the DPCH are changed, the RNC will choose an SF16 subtree that are not
used by HS-PDSCH from right to left. The selected subtree must meet the following conditions:
The selected subtree belongs to the code trees that can be shared between HS-PDSCH and DPCH.
The number of DPCHs and F-DPCHs on the selected subtree is smaller than or equal to the threshold
specified by the parameter CodeAdjForHsdpaUserNumThd.
The parameter CodeAdjForHsdpaUserNumThd limits the number of users that can be reshuffled
each time, to prevent too many users from being reshuffled in a short time and therefore to avoid
affecting user experience.
When the above conditions are met, the RNC will select this subtree for reshuffling and relocate the
users to the positions where the codes are idle.
Issue 04 (2013-05-10)
3-8
WCDMA RAN
HSDPA
3 Control Plane
Issue 04 (2013-05-10)
3-9
WCDMA RAN
HSDPA
4 User Plane
4 User Plane
This chapter consists of the following sections:
MAC-hs Scheduling
HARQ
TFRC Selection
Modulation Scheme
Issue 04 (2013-05-10)
4-1
WCDMA RAN
HSDPA
4 User Plane
If the buffering time is too short, you can infer that the RNC slows down the data transmission, that is,
the Iub transmission rate is lower than the Uu transmission rate. In this case, the pre-allocated Iub
bandwidth is adjusted to a value greater than the average Uu transmission rate.
If the buffering time is appropriate, the pre-allocated Iub bandwidth is adjusted to the average Uu
transmission rate.
If the buffering time is too long, the pre-allocated Iub bandwidth is adjusted to a value smaller than the
average Uu transmission rate.
For details on flow control, see Transmission Resource Management Feature Parameter Description.
For the Iur interface, flow control and congestion control are also applied. The control principles and processing
procedures are the same as those for the Iub interface.
Issue 04 (2013-05-10)
4-2
WCDMA RAN
HSDPA
4 User Plane
The data buffered in the NodeB is lost when the HS-DSCH serving cell changes.
Therefore, HARQ retransmission cannot totally replace RLC retransmission, which is described in 3GPP
TS 25.322. For services with high requirements for data transmission reliability, Huawei recommends
that the RLC acknowledged mode (AM) also be used to ensure correct transmission on the Uu interface
even when the services such as the BE service are carried on HSDPA channels.
Before the introduction of HSDPA, the size of an RLC PDU is usually 336 bits, where 320 bits are for the
payload and 16 bits for the RLC header. Without additional overhead, the MAC PDU is of the same size
as the RLC PDU. According to the 3GPP specifications, a maximum of 2,047 RLC PDUs can be
transmitted within an RLC window, and the RTT at the RLC layer is about 100 ms (50 TTIs).
In this condition, the maximum peak rate can only be 336 bits x (2047/50)/2 ms = 6.88 Mbit/s. To reach
higher rates, an RLC PDU of 656 bits is introduced, where 640 bits are for the payload and 16 bits for the
RLC header. The RLC PDU size can be set for each typical service. For high-speed services, the size is
set to 656 bits by default.
In addition, the RLC PDU size is fixed to 656 bits, and a transport block of 27,952 bits can contain a
maximum of 42 PDUs. Therefore, the maximum RLC payload rate is (656 bits - 16 bits) x 42/2 ms =
13.44 Mbit/s.
For example, 3GPP specifies that the UE of category 10 can use a maximum of 15 codes and receive a
transport block with a maximum of 27,952 bits. For details, see 3GPP TS 25.306. Therefore, the
theoretical peak rate is 27952 bits/2 ms = 13.976 Mbit/s. In practice, the radio channel quality,
retransmission probability, and available power also need to be considered. Therefore, the UE of
category 10 cannot reach 13.44 Mbit/s at the RLC layer in most tests.
A fixed RLC PDU size results in lower transmission efficiency due to unnecessary filler data and
redundant RLC PDU headers. Another reason why a fixed RLC PDU size is not desirable is that
high-speed transmission requires a large RLC PDU size required whereas edge coverage requires a
small RLC PDU size. Downlink layer 2 enhancement can be used to address these problems.
With downlink layer 2 enhancement, the RLC AM entity supports a variable PDU size, and the RLC layer
does not segment upper-layer packets whose sizes are smaller than the maximum RLC PDU size. The
RLC layer can flexibly adapt to traffic variations and reduce the overheads caused by RLC PDU headers.
For details about downlink layer 2 enhancement, see HSPA Evolution Feature Parameter Description.
Issue 04 (2013-05-10)
4-3
WCDMA RAN
HSDPA
4 User Plane
With the limited Uu resources for HSDPA in a cell, the user expects to maximize the service rate while
the telecom operator expects to maximize the system capacity. MAC-hs scheduling is used to coordinate
the Uu resources, user experience, and system capacity. It is implemented at the NodeB MAC-hs.
The scheduling algorithm consists of two steps. At first, the algorithm determines which initial
transmission queues or retransmission processes can be put into the candidate set for scheduling. Then,
the algorithm calculates their priorities based on factors such as the CQI, user fairness, and
differentiated services. If the algorithm is weighted more towards the channel quality of the UE, the
HSDPA cell can have a higher capacity but user fairness and differentiated services may be affected. If
the algorithm is weighted more towards user fairness and differentiated services, the system capacity
may be affected.
Huawei provides five scheduling algorithms: maximum C/I (MAXCI), round-robin (RR), proportional fair
(PF), Enhanced Proportional Fair (EPF), and EPF based on UE location (EPF_LOC). The EPF and
EPF_LOC are optional.
If the UE starts the compressed mode, its data cannot be put into the candidate set during the GAP.
If the UE category requires the UE to wait for several TTIs before it can be scheduled again, its data
cannot be put into the candidate set in this period. The UE of category 1 or 2 needs to wait for 3 TTIs,
and the UE of category 3, 4, and 11 must wait for 2 TTIs.
If the number of retransmissions of a data packet reaches or exceeds the maximum number, the data
of this UE cannot be put into the candidate set. The data should be discarded.
Huawei supports that the maximum number of retransmissions is set on a service basis:
MaxNonConverHarqRt:
CELL_DCH state
MaxEfachHarqRt:
The UE in the enhanced CELL_FACH state does not report ACK, NACK, or CQI
in the uplink. The HARQ processes of the UE use the blind retransmission mechanism. The
maximum number of retransmissions for the UE in Enhanced CELL_FACH Operation is specified by
this parameter.
The uplink channel quality of UEs is poor and the uplink channels of these UEs are carrying PS
conversational services or SRBs.
The MAC-hs can schedule data packets and select Transport Format and Resource Combine (TFRC) entities for UEs
whose uplink channel quality is poor and CQI is not 0 when the following conditions are met:
The MAC-hs queue contains the data packets of these UEs and the data size is not 0.
For new data packets, the MAC-hs calculates the scheduling priority for the follow-up data packet scheduling and TFRC
entity selection based on the principle that applies to a CQI of 12 (CQI adjustments are not performed). For data packets
to be retransmitted, the MAC-hs schedules these data packets and selects TFRC entities in the same way as it operates
on UEs with good uplink channel quality.
Issue 04 (2013-05-10)
4-4
WCDMA RAN
HSDPA
4 User Plane
MAXCI
RR
PF
EPF
EPF_LOC
Service type
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Maximum power
No
No
No
Yes
Yes
Waiting time
No
Yes
No
Yes
Yes
CQI
Yes
No
Yes
Yes
Yes
Actual throughput
No
No
Yes
Yes
Yes
SPI
No
No
No
Yes
Yes
SPI Weight
No
No
No
Yes
Yes
GBR
No
No
No
Yes
Yes
HBR
No
No
No
Yes
Yes
UE Location
No
No
No
No
Yes
MAXCI
RR
PF
EPF
EPF_LOC
System capacity
Highest
High
Higher
Higher
Higher
User fairness
Guaranteed
Guaranteed Not
guaranteed
Differentiated services
Real-time services
MAXCI Algorithm
The retransmission processes unconditionally have higher priorities than the initial transmission queues.
The retransmission processes are sorted in first-in first-out (FIFO) mode. The initial transmission queues
are sorted in the CQI order. A higher CQI means a higher data priority.
The MAXCI algorithm aims to maximize the system capacity but cannot ensure user fairness and
differentiated services.
The UE estimates the CQI based on the assumption that the transmit power of the HS-PDSCH on the
network side is as follows:
4-5
WCDMA RAN
HSDPA
4 User Plane
where
is the reference power adjustment. It is set to 0 in most cases. For details, see 3GPP TS 25.214.
RR Algorithm
The retransmission processes unconditionally have higher priorities than the initial transmission queues.
The retransmission processes are sorted in FIFO mode. The initial transmission queues are sorted in the
order of the waiting time in the MAC-hs queue. A longer waiting time means a higher data priority.
The RR algorithm aims to ensure user fairness but cannot provide differentiated services. Not
considering the CQI reported by the UE leads to lower system capacity.
PF Algorithm
The retransmission processes unconditionally have higher priorities than the initial transmission queues.
The retransmission processes are sorted in FIFO mode. The initial transmission queues are sorted in the
order of R/r. Here, R represents the throughput corresponding to the CQI reported by the UE, and r
represents the throughput achieved by the UE. A greater R/r value means a higher data priority.
The PF algorithm aims to make a tradeoff between system capacity and user fairness. It provides the
user with an average throughput that is proportional to the actual channel quality. The system capacity
provided by PF is between the system capacity provided by RR and that provided by MAXCI.
EPF Algorithm
The EPF algorithm (WRFD-01061103 Scheduling based on EPF and GBR) is an enhanced algorithm
developed based on the PF algorithm. The EPF algorithm defines more priorities than the PF algorithm
to better meet the QoS requirements of different services. The EPF algorithm can meet the requirements
of telecom operators related to user fairness and differentiated services and also provide a high system
capacity.
The EPF algorithm follows certain criteria to prioritize queues:
Service types are the first to be considered. They are prioritized in a sequence: SRB and IMS > voice
services > streaming services > BE services.
Guaranteed
bit rate (GBR) queues that have not arrived are prioritized over GBR queues that have
already arrived.
Queues
with high SPI weights are prioritized over those with low SPI weights.
High
bit rate (HBR) queues that have not arrived are prioritized over HBR queues that have already
arrived.
EFP algorithm guarantees the user fairness in the same way as that PF algorithm. HBR and Resource
Limit is used in EPF to limit the use of single users and improve fairness.
HBR is used to determine the throughput expected by the user based on a study on user experience.
When
the rate for a user reaches the HBR, the scheduling probability for the user is decreased. The
HBR is specified by the parameter HappyBR on the RNC side.
Resource Limit is used to prevent the users in areas with poor coverage from consuming too many cell
resources so that there is no decrease in system capacity.
Issue 04 (2013-05-10)
4-6
WCDMA RAN
HSDPA
4 User Plane
When
the resource limitation switch (RscLmSw) is on, the algorithm allocates the lowest priority to a
queue whose power consumption exceeds the threshold. If the power available to the queue is
limited, the queue's priority is always considered as meeting the GBR. The ratio of the maximum
available power of a queue to the total power of the cell is specified by the NodeB MML command
SET RSCLMTPARA.
SPIweight
The SPI weight affects the calculation of queue priorities. It is used to quantify the differentiated
services. If resource is insufficient, the proportion of SPI weights determines the approximate
proportion of rates among users. For example, for three throughput-sensitive service users with the
same channel quality, the same GBR and the proportion of SPI weights is 100:50:30, the proportion of
actual rates is close to 100:50:30.
For details on the parameters related to QoS management, such as the GBR, SPI, SPI weight, and HBR,
see QoS Management Feature Parameter Description.
EPF_LOC Algorithm
UEs' location in a cell can be defined as a near, middle, or far distance from the NodeB. HSDPA UEs
closer to the NodeB have better channel environments and report higher CQIs, as shown in Figure 4-2.
Figure 4-2 UE locations and CQIs
With the EPF/PF algorithm, UEs that have the same SPI weight value but are at different distances from
the NodeB have roughly equal scheduling opportunities.
The EPF_LOC algorithm (WRFD-140221 HSDPA Scheduling based on UE Location) builds on the EPF
algorithm and considers UE locations as HSDPA scheduling weights. While ensuring GBRs for all UEs,
the EPF_LOC algorithm gives more scheduling opportunities to UEs that are close to the NodeB in order
to improve throughput for these UEs. Since these UEs can obtain larger transmission blocks than UEs
farther from the NodeB, the overall throughput of the cell is improved.
CQIs indirectly reflect UE locations. A CQI reported by a UE implies the UE's location, a near, middle, or
far distance either between the UE and the NodeB, or between the UEs within a cell. Assuming that
there are two UEs far from the NodeB and the CQIs reported by them are 15 and 13, respectively, the
UE that reports the CQI 15 has more scheduling opportunities and higher downlink throughput.
Issue 04 (2013-05-10)
4-7
WCDMA RAN
HSDPA
4 User Plane
The PF and EPF algorithms consider the value R/r, where R is the throughput corresponding to the CQI reported by the
UE. The EPF_LOC algorithm is based on the EPF algorithm. In addition to R/r, the EPF_LOC algorithm also considers UE
locations indicated by CQIs.
If a larger value is set for the LOCWEIGHT parameter, UE locations weigh more in the EPF_LOC
algorithm. Theoretically, this results in a higher downlink throughput of the cell and greater differentiation
between UEs at different distances from the NodeB. UEs closer to the NodeB have more scheduling
opportunities and higher throughput, which is the other way around for UEs farther from the NodeB.
UEs closer to the NodeB have more scheduling opportunities and therefore higher throughput. This
improves the cell throughput.
UEs farther from the NodeB have fewer scheduling opportunities and therefore lower throughput.
To ensure user experience at cell edges, it is recommended that GBRs be configured for all BE services.
To configure GBRs, run the SET UUSERGBR command on the RNC.
The LOCWeight and SPIWeight parameters simultaneously affect HSDPA scheduling weights. UEs far from the NodeB
will experience decreased downlink rates after this feature is activated. If high rates need to be ensured for gold users, it is
recommended that higher GBRs or SPI weight values be set for gold users.
The EPF_LOC algorithm gives more scheduling opportunities to UEs closer to the NodeB and increases
the downlink overall throughput of the cell. Cell throughput gains relate to UEs' CQIs. With EPF_LOC
algorithm, HSDPA UEs at cell edges have fewer scheduling opportunities and lower throughput. If GBRs
are not configured for BE services, HSDPA UEs at cell edges may have to wait a long time before they
have scheduling opportunities. As a result, traffic radio bearers (TRBs) are more likely to reset and the
call drop rate increases. The magnitude of this impact depends on factors such as UE location
distribution and service distribution in the cell. It is recommended that GBRs be configured for BE
services to ensure network performance.
The feature of time and HS-PDSCH codes multiplex enables the allocation of different codes in the same
TTI to different users or the time division multiplexing of the same code in different TTIs for different
users to provide the utilization of code resources and the system throughput.
Issue 04 (2013-05-10)
4-8
WCDMA RAN
HSDPA
4 User Plane
The parallel data transmission of multiple users over HS-DSCH requires more HS-SCCH codes and
HS-PDSCH codes within a single TTI. Code multiplexing is adopted and is found useful when the NodeB
has more HS-PDSCH codes for allocation than those supported by the UE. For instance, the UE
supports 5 codes and the NodeB has 10 codes available in a single TTI. The code multiplexing can
increase the resource utilization and system throughput.
4.4 HARQ
The main purpose of introducing HARQ is to reduce the retransmission delay and improve the
retransmission efficiency. HARQ enables fast retransmission at the physical layer. Before decoding, the
UE combines the retransmitted data and the previously received data, making full use of the data
transmitted each time. In addition, HARQ can fine-tune the effective rate to compensate for the errors
made by TFRC section.
If the UE reports an ACK, the NodeB transmits the next new data.
If the UE reports an NACK, the NodeB retransmits the original data. After receiving the data, the UE
performs soft combining of this data and the data received before, decodes the combined data, and
then reports an ACK or NACK to the NodeB.
RLC retransmission on the DCH involves the RNC, and therefore the RTT is relatively long. In
comparison, HARQ involves only the physical layer and MAC-hs of the NodeB and those of the UE, and
therefore the RTT is reduced to only 6 TTIs (12 ms).
After a transmission, the HARQ process must wait at least 10 ms before it can transmit the next new
data or retransmit the original data. Therefore, to improve transmission efficiency, other HARQ
processes can transmit data during the waiting time. A maximum of six HARQ processes can be
configured in each of the NodeB HARQ entity and the UE HARQ entity. Note that not all UE categories
support six HARQ processes. For example, the UEs of some categories can receive data every one or
two TTIs. Therefore, only two or three HARQ processes can be configured. The RAN can automatically
choose the most appropriate configuration based on UE capability.
Figure 4-4 HARQ retransmission principles
Issue 04 (2013-05-10)
4-9
WCDMA RAN
HSDPA
4 User Plane
Issue 04 (2013-05-10)
4-10
WCDMA RAN
HSDPA
4 User Plane
Determining the amount of data that can be transmitted by the queue or queues
If the parameter is set to Code_Pri, the TFRC algorithm prefers the use of codes. Under the
precondition that the transport block with the TBS is large enough to carry the buffered data, the
algorithm first reduces the power. If the corresponding CQI decreases to the smallest one but the
precondition is still met, the algorithm attempts to reduce the number of codes. This setting is
applicable the outdoor macro base station with limited power.
If the parameter is set to Power_Pri, the TFRC algorithm prefers the use of power. Under the
precondition that the transport block with the TBS is large enough to carry the buffered data, the
algorithm first reduces the number of codes. If the number of codes decreases to 1 but the
precondition is still met, the algorithm attempts to reduce the power. This setting is applicable to indoor
application with limited codes.
If the parameter is set to PowerCode_Bal, the TFRC algorithm balances the use of power and the use
of codes. Under the precondition that the transport block with the TBS is large enough to carry the
buffered data, the algorithm reduces the power and codes in a balanced mode. This setting protects
the codes or power from being used up, improving the resource usage and increasing the cell
capacity.
Figure 4-6 shows the backward-searching methods used when the parameter is set to Code_Pri or
Power_Pri.
Issue 04 (2013-05-10)
4-11
WCDMA RAN
HSDPA
4 User Plane
Figure 4-6 Backward-searching methods used when the parameter is set to Code_Pri or Power_Pri
Figure 4-7 shows the backward-searching methods used when the parameter is set to PowerCode_Bal.
Figure 4-7 Backward-searching methods used when the parameter is set to PowerCode_Bal
Issue 04 (2013-05-10)
4-12
WCDMA RAN
HSDPA
4 User Plane
With the increase in downlink power, the downlink load is also increased. When the downlink load
becomes heavy, network KPIs are deteriorated. Therefore, the RESVERD3 parameter cannot be set to a
too large value.
Before enabling the HSDPA remaining power appending algorithm, ensure that HSDPA has been
enabled on the network and that UEs support HSDPA.
When the RESVERD3 parameter is set to 0, the HSDPA remaining power appending algorithm does not take effect.
When the CQI adjustment based on a fixed IBLER(Initial Block Error Rate) target algorithm is enabled on the NodeB, the
HSDPA remaining power appending algorithm does not take effect. IBLER stands for initial block error rate.
Overview
The CQI measures the channel conditions of a UE and is reported from the UE to the NodeB. Without
this feature, the NodeB determines an appropriate TBS based on the reported CQI, system resources,
and the TFRC policy. If the reported CQI and related conditions remain the same, the NodeB does not
change the TBS because it does not consider the ever-changing radio environments.
The constant changes in radio environments, caused by multipath effects and UE mobility, lead to
fluctuating channel quality. Under these circumstances, choosing a TBS based on the reported CQI
makes it difficult to always achieve the optimum downlink throughput.
With the feature CQI adjustment based on dynamic BLER target, the NodeB monitors the channel
quality fluctuations for HSDPA users in a cell in real time and dynamically selects a proper BLER target
based on the monitoring result. The NodeB then uses the BLER target to adjust the CQI reported by the
UE. Based on the adjusted CQI, the NodeB determines an appropriate TBS to achieve higher downlink
throughput for HSDPA users and higher cell throughput.
The BLER described in this section refers to the SBLER at the MAC-(e)hs layer and reflects the average block error rate
at the MAC layer. Accordingly, the BLER target described in this section refers to the SBLER target at the MAC-(e)hs
layer.
The required BLER target may be high in some environments; therefore this feature is not suitable for
networks that limit the BLER target.
This feature requires that both the network and UE support HSDPA. This feature is applicable to all
HSDPA terminals except for the terminals that are configured with MIMO. Different terminals may have
different performance for the same TB size. Some terminals may have greater BLERs. This feature
adjusts the TB size for terminals based on data transmission performance to achieve optimized
performance.
This feature can be enabled by selecting the CQI_ADJ_BY_DYN_BLER check box under the
CQIADJALGOFNONCON parameter.
Issue 04 (2013-05-10)
4-13
WCDMA RAN
HSDPA
4 User Plane
3. Based on the ACK, NACK, or DTX indication from the UE in the current TTI and on the optimum
BLER target, the NodeB calculates the CQI offset, which can be a positive or negative number. The
NodeB then uses the CQI offset to adjust the CQI.
4. Based on the adjusted CQI, the NodeB selects an appropriate TBS by using the TFRC algorithm.
Scenario 2: The UE is processing burst services, for example, the UE is browsing web sites, sending
heartbeat packets, microblogging, or using the QQ application.
If the NodeB uses the CQI that is reported by the UE when the UE does not process any data, the
NodeB regards that the interference between channels is not strong. When the UE starts processing
data, the BLER may be high, prolonging the delay and affecting the burst service throughput.
The BLER Optimization for HSDPA Burst Services function calculates the interference of a UE when the
UE reports a CQI to the NodeB and calculates the interference when the UE starts data transmission.
Then, this function works out the interference difference in the two scenarios. Based on the difference,
this function adjusts the CQI. By doing this, the NodeB can use an appropriate CQI when the UE is
engaged in initial HSDPA data transmission or is processing burst services. This helps reduce the BLER
and increase burst service throughput.
The BLER Optimization for HSDPA Burst Services function is controlled by the RESVERD1:RSVDBIT29
parameter in the SET LOCELLRSVP command.
To use this function, the target network must support HSDPA and some UEs are HSDPA-capable. This
function takes effect on all HSDPA-capable UEs.
When the UE is in the unfavorable radio environment, the transmission can adopt the low-order QPSK
modulation mode and small transport blocks to ensure communication quality.
When the UE is in the favorable radio environment, the transmission can adopt the high-order 16QAM
modulation scheme and large transport blocks to reach a high peak rate.
QPSK modulation is a basic downlink data modulation function that is used after HSDPA is introduced.
Compared with the QPSK modulation scheme, the 16QAM modulation scheme is a higher-order
downlink data modulation scheme. This feature enables the peak rate on the Uu interface to reach 14.4
Mbit/s.
64QAM
3GPP R5 introduces 16QAM to increase the peak rate per user and expands the system capacity,
whereas 64QAM introduced in 3GPP R7 protocols is a further enhancement of 16QAM.
With downlink 64QAM, a higher-order modulation scheme than 16QAM can be used when the channel
is of higher quality. Theoretically, 64QAM supports a peak data rate of 21 Mbit/s and at the same time
increases the average throughput of the system. Simulation shows that compared with 16QAM, 64QAM
Issue 04 (2013-05-10)
4-14
WCDMA RAN
HSDPA
4 User Plane
can increase the average throughput by 7% and 16% respectively in macro cell and in micro cell, if the
UEs in the cells use the type 3 receivers.
The 3GPP R7 protocols define the categories of the UEs that support 64QAM, and add the information
elements (IEs) that support 64QAM in the reporting of local cell capability. The RNC determines whether
the RL between the NodeB and the UE supports 64QAM according to the local cell capability reported by
the NodeB and the UE capability. If the RL supports 64QAM, the MAC-hs scheduler of the NodeB
determines every 2 ms whether to use 64QAM according to the following aspects:
Compared with the 16QAM modulation scheme, the 64QAM modulation scheme is a higher-order
downlink data modulation scheme. This feature enables the peak rate on the Uu interface to reach 21
Mbit/s.
Issue 04 (2013-05-10)
4-15
WCDMA RAN
HSDPA
QoS Management
Diff-Serv Management
The conversational service (including the CS voice and VoIP) has a relatively high requirement for
service delay and a certain requirement for BLER.
The streaming service has a requirement for guaranteed bit rate (GBR).
The FTP service has a high requirement for BLER and error-free transmission. In addition, this service
requires higher service rates to provide better user experience.
The HTTP service has a high requirement for error-free transmission and a certain requirement for
response delay. In addition, this service requires shorter delay to provide better user experience.
HSDPA QoS management is implemented by related HSDPA functions. The following table lists the
relationships between HSDPA functions and QoS indicators.
Table 5-1 Relationships between HSDPA functions and QoS indicators
Function
Service Connectivity
Service Delay
Service Rate
Mobility management
Load control
RLC retransmission
Flow control
BLER
Congestion control
HARQ
MAC-hs scheduling
TFRC selection
These relationships between HSDPA functions and QoS indicators are described as follows:
Mobility management
Service continuity is implemented by mobility management.
For details, see section 3.3 "Mobility Management" and Handover Feature Parameter Description.
Issue 04 (2013-05-10)
5-1
WCDMA RAN
HSDPA
Bearer mapping
HSDPA bearers increase the service rate greatly and reduce the service delay.
For details, see section 3.1 "Bearer Mapping."
Load control
The network resources are limited. Therefore, when a large number of users attempt to access the
network, the access control function is required to control the access to ensure the QoS of the
admitted users.
The network resources consumed by the admitted users vary with the changed channel qualities,
which may lead to network congestion. To relieve congestion, the overload control function is required
to ensure the QoS of most users.
For details on load control, see Load Control Feature Parameter Description.
MAC-hs scheduling
Based on the waiting time, achieved service rate, and GBR, the MAC-hs scheduling function sorts the
users to meet the requirements for transmission delay and transmission rate on the Uu interface. For
details, see section 4.3 "MAC-hs Scheduling."
TFRC selection
Based on the available power, available codes, actual channel quality, and actual data amount, the
TFRC selection function selects appropriate transport blocks and modulation schemes to increase
data rates. For details, see section 4.5 "TFRC Selection."
To further quantify the effect of Diff-Serv management, differentiated services based on SPI weights
(WRFD-020806 Differentiated Service Based on SPI Weight) are introduced.
Issue 04 (2013-05-10)
5-2
WCDMA RAN
HSDPA
6 Related Features
6 Related Features
6.1 WRFD-010610 HSDPA Introduction Package
6.1.1 Prerequisite Features
None
Issue 04 (2013-05-10)
6-1
WCDMA RAN
HSDPA
6 Related Features
Issue 04 (2013-05-10)
6-2
WCDMA RAN
HSDPA
7 Network Impact
7 Network Impact
7.1 WRFD-010610 HSDPA Introduction Package
7.1.1 System Capacity
After activating HSDPA Introduction Package, the downlink cell throughput, downlink cell capacity, and
downlink data rate (which can reach up to 13.9 Mbit/s at the MAC layer for each HSDPA UE) increase.
HSDPA Introduction Package adjusts the downlink power and data rate based on channel quality,
maximizing the power resource utilization.
Shorter delay
With TTIs of 2 ms and 10 ms, which provide shorter scheduling intervals, the fast scheduling algorithm
enables the NodeB to quickly schedule and retransmit data.
Issue 04 (2013-05-10)
7-1
WCDMA RAN
HSDPA
7 Network Impact
Issue 04 (2013-05-10)
7-2
WCDMA RAN
HSDPA
8 Engineering Guidelines
8 Engineering Guidelines
8.1 WRFD-010610 HSDPA Introduction Package
8.1.1 When to Use HSDPA Introduction Package
HSDPA can significantly increase the downlink peak rate per user, shorten the round trip delay, and
expand the system capacity. This feature package provides the basic functions of HSDPA to meet the
requirements for test or trial operation of HSDPA services.
Prerequisites
Dependencies on Hardware
NDLP
The
UE is HSDPA-capable.
License
The license "High Speed Downlink Packet Access" on the BSC6900 side has been activated. For
details about how to activate the license, see License Management Feature Parameter Description.
Procedure
Activation Procedure
1. Run the BSC6900 MML command ADD UCELLHSDPA to set HSDPA-related parameters based on
the network plan.
2. Run the BSC6900 MML command ACT UCELLHSDPA to activate this feature.
3. Configure Iub transport for HSDPA.
In
an ATM network:
a.
b.
c.
d.
In
Run the BSC6900 MML command ADD ATMTRF to configure new records of ATM traffic based
on network planning requirements.
Run the BSC6900 MML command LST TRMMAP to query the transmission resource mapping.
Run the BSC6900 MML command ADD AAL2PATH to set associated parameters according to
the network plan. TX traffic record index and RX traffic record index of the AAL2 path to be
added must be the same as those set in the ADD ATMTRF command. In addition, AAL2 Path
Type should be set according to the mapping between service types and AAL paths.
Run the NodeB MML command ADD AAL2PATH to configure an AAL2 path for HSDPA based
on network planning requirements.
an IP network:
Issue 04 (2013-05-10)
8-1
WCDMA RAN
HSDPA
a.
8 Engineering Guidelines
Run the BSC6900 MML command LST ADJMAP to query whether resource management
mapping is configured for the adjacent node.
If configured, check the TRMMAP index of the adjacent node.
If not configured, run the BSC6900 MML command LST TRMMAP to query the default
TRMMAP ID used by the adjacent node based on the settings of Interface Type and
Transport Type. For example, if Interface Type is set to Iub Interface, then TRMMAP ID
is 1.
b.
Run the BSC6900 MML command LST TRMMAP to check whether the IP path mapping to the
HSDPA service is configured according to the TRMMAP ID used by the adjacent node.
If configured, no further action is required.
If not configured, run the BSC6900 MML command ADD IPPATH to configure the IP path
mapping to the HSDPA service.
To ensure that HSDPA services can be set up successfully, HSDPA services must be mapped to the corresponding AAL2
paths or IP paths. To avoid the affect on ongoing services, you can add new AAL2 paths or IP paths.
Verification Procedure
Run the BSC6900 MML command DSP UCELL to check whether this feature is activated. If HSDPA
Operational State is set to Enabled, this feature has been activated.
Deactivation Procedure
1. Run the BSC6900 MML command DEA UCELLHSDPA to deactivate this feature.
2. Run the BSC6900 MML command DSP UCELL to check whether the HSDPA feature is deactivated.
If HSDPA Operational State is set to Disabled, this feature has been deactivated.
Example
// Setting HSDPA-related parameters
ADD UCELLHSDPA: CellId=3000, AllocCodeMode=Automatic, HsPdschMaxCodeNum=4, HsPdschMinCodeNum=1,
CodeAdjForHsdpaSwitch=ON;
//Activating HSDPA Introduction Package
ACT UCELLHSDPA: CellId=3000;
//Configuring Iub transport for HSDPA
//ATM network
ADD ATMTRF: TRFX=118, ST=RTVBR, UT=KBIT/S, PCR=5150, SCR=5149, REMARK="5M-for-HSDPA";
ADD AAL2PATH: ANI=10, PATHID=2, CARRYT=IMA, CARRYF=1, CARRYSN=0, CARRYIMAGRPN=1, RSCGRPFLAG=NO, VPI=13,
VCI=71, TXTRFX=118, RXTRFX=118, AAL2PATHT=HSPA;
//Adding an AAL2 path
ADD AAL2PATH: PATHID=2, SN=12, SBT=BASE_BOARD, PT=IMA, VPI=13, VCI=71, ST=RTVBR, PCR=5150, SCR=5149,
RCR=5150, NT=LOCAL, PAT=H_NRT;
//IP network
ADD IPPATH: ANI=0, PATHID=1, ITFT=IUB, TRANST=IP,PATHT=BE, IPADDR="80.1.1.1", PEERIPADDR="10.161.0.1",
PEERMASK="255.255.255.0", TXBW=1000, RXBW=1000;
//Verifying HSDPA Introduction Package
DSP UCELL: DSPT=BYCELL, CellId=3000, LstFormat=VERTICAL;
//Deactivating HSDPA Introduction Package
DEA UCELLHSDPA: CellId=3000;
DSP UCELL: DSPT=BYCELL, CellId=3000, LstFormat=VERTICAL;
8-2
WCDMA RAN
HSDPA
8 Engineering Guidelines
Counter Name
NE
Counter Description
VS.HSDPA.UE.Mean.Cell
RNC
VS.HSDPA.UE.Max.Cell
RNC
Counter Name
NE
Counter Description
VS.SRNCIubBytesPSR99C
onv.Tx
RNC
VS.SRNCIubBytesPSR99S
tr.Tx
RNC
VS.SRNCIubBytesPSR99I
nt.Tx
RNC
VS.SRNCIubBytesPSR99B
kg.Tx
RNC
VS.SRNCIubBytesHSDPA.
Tx
RNC
VS.SRNCIubBytesCSConv
.Tx
RNC
Prerequisites
Dependencies on Hardware
This feature does not have any special requirements for hardware.
Issue 04 (2013-05-10)
8-3
WCDMA RAN
HSDPA
8 Engineering Guidelines
The configurations of the features on which this feature depends are complete. This feature depends
on the feature WRFD-010610 HSDPA Introduction Package.
License
The license "HSDPA RRM package 1" and "HSDPA function" on the NodeB side has been activated.
For details about how to activate the license, see License Management Feature Parameter
Description.
Procedure
Activation Procedure
1. Run the BSC6900 MML command MOD UCELLHSDPA (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell HSDPA Parameters; CME batch modification
center: Modifying UMTS Cell Parameters in Batches) to set Code Number for HS-SCCH to 1.
The BSC6900 MML command MOD UCELLHSDPA (CME single configuration: UMTS Cell Configuration Express >
Cell Parameters > Cell HSDPA Parameters; CME batch modification center: Modifying UMTS Cell Parameters in
Batches) fails to be executed when HSDPA is activated. Therefore, run the BSC6900 MML command DEA
UCELLHSDPA (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell HSDPA
Parameters. Set ACTSTATUS to Deactivated; CME batch configuration: No supported) to deactivate HSDPA before
configuring this feature and run the BSC6900 MML command ACT UCELLHSDPA (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell HSDPA Parameters. Set ACTSTATUS to Activated; CME batch
configuration: No supported) to reactivate HSDPA after configuring this feature.
The BSC6900 MML command MOD UCELLHSDPA (CME single configuration: UMTS Cell Configuration Express >
Cell Parameters > Cell HSDPA Parameters; CME batch modification center: Modifying UMTS Cell Parameters in
Batches) fails to be executed when CELL-FACH enhancement is activated. Therefore, run the BSC6900 MML command
DEA UCELLEFACH (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell
Enhanced FACH parameters. Set Validation indication to Deactivated; CME batch configuration: No supported) to
deactivate enhanced CELL-FACH before configuring this feature and Run the BSC6900 MML command ACT
UCELLEFACH (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Enhanced
FACH parameters. Set Validation indication to Activated; CME batch configuration: No supported) to reactivate
enhanced CELL-FACH after configuring this feature.
By default, the number of HS-SCCH codes for each cell is 4. If the default number is used, the HS-PDSCH can use only
14 SF16 codes. To enable the HS-PDSCH to use all 15 SF16 codes, run the BSC6900 MML command MOD
UCELLHSDPA (CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell HSDPA
Parameters; CME batch modification center: Modifying UMTS Cell Parameters in Batches) to set the value of Code
Number for HS-SCCH to 1.
2. Run the BSC6900 MML command MOD UCELLHSDPA (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell HSDPA Parameters; CME batch modification
center: Modifying UMTS Cell Parameters in Batches) to set Allocate Code Mode to Manual(Manual)
and Code Number for HS-PDSCH to 15.
Verification Procedure
1. Initialize UMTS monitoring on the BSC6900 LMT, as shown in Figure 6-1. Click Submit. A real-time
monitoring window is displayed.
Issue 04 (2013-05-10)
8-4
WCDMA RAN
HSDPA
8 Engineering Guidelines
2. Check whether 15 SF16 codes are occupied by the HS-PDSCH in the Cell Performance Monitoring
window.
Expected result: The HS-PDSCH occupies 15 SF16 codes.
Deactivation Procedure
This feature does not need to be deactivated.
Example
//Verifying 15 Codes per Cell
MOD UCELLHSDPA: CellId=1, HsScchCodeNum=1;
MOD UCELLHSDPA: CellId=1, AllocCodeMode=Manual, HsPdschCodeNum=15;
Prerequisites
Dependencies on Hardware
This feature does not have any special requirements for hardware.
License
The license "HSDPA RRM package 1" and "HSDPA function" on the NodeB side has been activated.
For details about how to activate the license, see License Management Feature Parameter.
Description.
Issue 04 (2013-05-10)
8-5
WCDMA RAN
HSDPA
8 Engineering Guidelines
Procedure
Activation Procedure
This feature does not need to be activated.
Verification Procedure
This feature does not need to be verified.
Deactivation Procedure
This feature does not need to be deactivated.
Prerequisites
Dependencies on Hardware
This feature does not depend on the hardware.
License
The license "HSDPA RRM package 1" and "HSDPA function" on the NodeB side has been activated.
For details about how to activate the license, see License Management Feature Parameter
Description.
Procedure
Activation Procedure
1. Run the NodeB MML command SET MACHSPARA (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > Locell Algorithm Parameters > MAC
Parameters > MACHSPARA; CME batch modification center: Modifying Physical NodeB
Parameters in Batches) to set the parameter Scheduling Method to MAXCI(Max C/I Algorithm),
RR(Round Robin Algorithm) or PF(PF Algorithm).
Verification Procedure
Issue 04 (2013-05-10)
8-6
WCDMA RAN
HSDPA
8 Engineering Guidelines
1. Run the NodeB MML command LST MACHSPARA to query the settings of the parameter
Scheduling Method.
Deactivation Procedure
This feature does not need to be deactivated.
Example
//Activation procedure
SET MACHSPARA: LOCELL=0, SM=MAXCI;
//Verification procedure
LST MACHSPARA: LOCELL=0;
Prerequisites
Dependencies on Hardware
This feature does not depend on the hardware.
License
The license "HSDPA RRM package 1" and "HSDPA function" on the NodeB side has been activated.
For details about how to activate the license, see License Management Feature Parameter
Description.
Procedure
Activation Procedure
Run the BSC6900 MML command MOD UCELLHSDPA (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell HSDPA Parameters; CME batch modification
center: Modifying UMTS Cell Parameters in Batches). In this step, set Allocate Code Mode to
Manual or Automatic.
If
Allocate Code Mode is set to Manual, set Code Number for HS-PDSCH to specify the number of
HS-PDSCH codes.
Issue 04 (2013-05-10)
8-7
WCDMA RAN
HSDPA
8 Engineering Guidelines
If
Allocate Code Mode is set to Automatic, set Code Max Number for HS-PDSCH to specify the
maximum number of HS-PDSCH codes and set Code Min Number for HS-PDSCH to specify the
minimum number of HS-PDSCH codes.
Verification Procedure
1. Run the BSC6900 MML command LST UCELLHSDPA to query code allocation mode.
2. On the BSC6900 LMT, click to display Cell Performance Monitoring. Set Monitor Item to Cell
Code Tree Monitor and click Submit. The Cell Performance Monitoring tab page is displayed.
3. View the number of codes allocated to the HS-PDSCH in the cell. If Allocate Code Mode is set to
Manual, the monitoring window of cell code tree usage shows that the number of codes allocated to
the HS-PDSCH remains unchanged. If Allocate Code Mode is set to Automatic, the monitoring
window of cell code tree usage shows that the number of codes allocated to the HS-PDSCH varies
with service access requests in the cell. For example, the number of codes allocated to the
HS-PDSCH increases with the increase of HSDPA access requests and decreases with the
decrease of HSDPA access requests.
Deactivation Procedure
This feature does not need to be deactivated.
Example
//Activating HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation
MOD UCELLHSDPA: CellId=11, AllocCodeMode=Manual, HsPdschCodeNum=5, HsScchCodeNum=4;
MOD UCELLHSDPA: CellId=11, AllocCodeMode=Automatic, HsPdschMaxCodeNum=5, HsPdschMinCodeNum=1;
Prerequisites
Dependencies on Hardware
This feature does not depend on the hardware.
License
The license "HSDPA RRM package 1" and "HSDPA function" on the NodeB side has been activated.
For details about how to activate the license, see License Management Feature Parameter
Description.
Issue 04 (2013-05-10)
8-8
WCDMA RAN
HSDPA
8 Engineering Guidelines
Procedure
Activation Procedure
1. Run the NodeB MML command SET HSDPAFLOWCTRLPARA (CME single configuration: NodeB
Configuration Express > IUB_NodeB > ATM Transport Layer > ATMPort > HSDPA Flow
Control > HSDPA Flow Control Parameters; CME batch modification center: not supported) to set
the parameter Flow Control Switch to enable the NodeB HSDPA flow control function. The adaptive
flow control algorithm is recommended.
There are four types of HSDPA flow control algorithm as follows:
When
Flow Control Switch is set to STATIC_BW_SHAPING, the NodeB does not adjust the
available bandwidth for HSDPA users based on delay and packet loss on the Iub interface. Then,
subtracting Iub bandwidth used by R99 from Iub bandwidth configured, the NodeB performs Iub
shaping and distributes flow to HSDPA users.
When
Flow Control Switch is set to DYNAMIC_BW_SHAPING, the NodeB adjusts the available
bandwidth for HSDPA users based on delay and packet loss on the Iub interface. Then, considering
the data rate on the air interface, the NodeB performs Iub shaping and distributes flow to HSDPA
users.
When
Flow Control Switch is set to NO_BW_SHAPING, the NodeB does not adjust the bandwidth
based on delay and packet loss on the Iub interface. The NodeB reports the conditions about the air
interface to the RNC, and then the RNC allocates the bandwidth.
When
Flow Control Switch is set to BW_SHAPING_ONOFF_TOGGLE, the flow control policy for
the ports of the NodeB is either DYNAMIC_BW_SHAPING or NO_BW_SHAPING in accordance
with the congestion detection mechanism of the NodeB. This flow control algorithm is recommended.
Verification Procedure
1. Choose Monitor > UMTS Monitoring > Connection Performance Monitoring on the BSC6900
LMT. Create UL Throughput Bandwidth and DL Throughput Bandwidth tasks.
2. Assume that the current Iub bandwidth is 4 MHz and the bandwidth usage is 100%. Enable an
HSDPA-capable UE1 to access the network and originate a PS service. Record the throughput of
UE1.
Expected result:
The throughput of UE1 is 4 Mbps.
3. Enable an HSDPA-capable UE2 to access the network (with the same configuration as UE1) and
originate a download service. Record the throughput of the two UEs.
Expected result:
The throughput of UE1 decreases after UE2 accesses the network. When the throughput of the two
UEs is stable, the total bandwidth of the two UEs is 4 MHz. If user priority, service type and Security
Parameter Index (SPI) of the two UEs are the same, the final ratio of the two UEs' throughput is 1:1.
Deactivation Procedure
You can deactivate the current algorithm by selecting one of the other flow control algorithms.
Example
//Activating HSDPA Flow Control and setting the flow control mode to adaptive flow control
SET HSDPAFLOWCTRLPARA: SRN=0, SN=6, BEAR=ATM, SBT=BASE_BOARD, PT=IMA, PN=0, SWITCH=
BW_SHAPING_ONOFF_TOGGLE, TD=2, DR=1, ITM=TERRESTRIAL;
Issue 04 (2013-05-10)
8-9
WCDMA RAN
HSDPA
8 Engineering Guidelines
Prerequisites
Dependencies on Hardware
This feature does not have any special requirements for hardware.
License
The license "HSDPA RRM package 1" and "HSDPA function" on the NodeB side has been activated.
For details about how to activate the license, see License Management Feature Parameter
Description.
Procedure
Activation Procedure
The methods for activating intra-frequency, inter-frequency, and inter-RAT handovers are the same for
HSDPA users and R99 users. For details on how to activate the WRFD-01061006 HSDPA Mobility
Management feature, see chapter "Configuring Inter Frequency Load Balance" in Load Control Feature
Parameter Description or see the following sections in Handover Feature Parameter Description:
13.4
13.8
13.9
13.10
13.11
13.16
13.17
Verification Procedure
None
Deactivation Procedure
This feature does not need to be deactivated.
Issue 04 (2013-05-10)
8-10
WCDMA RAN
HSDPA
8 Engineering Guidelines
Prerequisites
Dependencies on Hardware
This feature does not have any special requirements for hardware.
License
The license "HSDPA RRM package 1" and "HSDPA function" on the NodeB side has been activated.
For details about how to activate the license, see License Management Feature Parameter
Description.
Procedure
Activation Procedure
This feature does not need to be activated.
Verification Procedure
This feature does not need to be verified.
Deactivation Procedure
This feature does not need to be deactivated.
Issue 04 (2013-05-10)
8-11
WCDMA RAN
HSDPA
8 Engineering Guidelines
Prerequisites
Dependencies on Hardware
This
UE
License
The license "HSDPA RRM package 1" and "HSDPA function" on the NodeB side has been activated.
For details about how to activate the license, see License Management Feature Parameter
Description.
Procedure
Activation Procedure
HSDPA Introduction Package must be activated before activating this feature. For the method of activating HSDPA
Introduction Package, see the section "Configuring HSDPA Introduction Package."
1. Run the NodeB MML command SET MACHSPARA (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > Locell Algorithm Parameters > MAC
Parameters > MACHSPARA; CME batch modification center: Modifying Physical NodeB
Parameters in Batches). In this step, set 16QAM Switch to OPEN(open).
Verification Procedure
For the 16QAM modulation of the HSDPA UE, the NodeB license control item must be enabled.
As defined in 3GPP 25.306, the UE in category 8 can support both QPSK and 16QAM modulation schemes. Only 16QAM
modulation, however, enables the throughput of category 8 UE to reach 5 Mbit/s.
Only in case of good environment quality of the channel, the throughput of category 8 UE can reach 5 Mbit/s.
Perform the following steps to check whether the download rate can reach 5 Mbit/s.
1. Use the UE to start a PS interactive service of DL 7200 kbit/s. The PS service is carried on the
HS-DSCH. The UE keeps in Cell-DCH state.
2. Start FTP (10 threads) to download given files, which are larger than 1 GB. By monitoring the DL
throughput and bandwidth, you find that the PS downloading service is normal and the bit rate is
higher than 5 Mbit/s.
Deactivation Procedure
1. Run the NodeB MML command SET MACHSPARA (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > Locell Algorithm Parameters > MAC
Parameters > MACHSPARA; CME batch modification center: Modifying Physical NodeB
Parameters in Batches). In this step, set 16QAM Switch to CLOSE(close).
Example
//Activating procedure
SET MACHSPARA: CME16QAMSW=OPEN;
//Deactivating procedure
SET MACHSPARA: CME16QAMSW=CLOSE;
Issue 04 (2013-05-10)
8-12
WCDMA RAN
HSDPA
8 Engineering Guidelines
Prerequisites
Dependencies on Hardware
This feature does not depend on the hardware.
License
The license "HSDPA RRM package 1" on the NodeB side has been activated. For details about how to
activate the license, see License Management Feature Parameter Description.
Procedure
Activation Procedure
HSDPA Introduction Package must be activated before activating this feature. For the method of activating HSDPA
Introduction Package, see the section "Configuring HSDPA Introduction Package."
1. Run the NodeB MML command SET MACHSPARA (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > Locell Algorithm Parameters > MAC
Parameters > MACHSPARA; CME batch modification center: Modifying Physical NodeB
Parameters in Batches). In this step, set Dynamic Code Switch to OPEN(open).
Verification Procedure
1. Run the NodeB MML command SET MACHSPARA. In this step, set Dynamic Code Switch to
CLOSE(close).
2. Run the BSC6900 MML command MOD UCELLHSDPA.
3. set Allocate Code Mode to Manual.
4. set Code Number for HS-PDSCH to 5.
5. Use a UE that belongs to category 8 or is capable of higher HSDPA performance to download 200
MB files from the FTP server in the serving cell.
6. Select Service > Trace Management > Interface Trace Task > User from the navigation tree in
Maintenance tab on NodeB LMT, select (DL)Hsdpa User Enhanced Schedule Data message, as
shown in Figure 8-2.
Issue 04 (2013-05-10)
8-13
WCDMA RAN
HSDPA
8 Engineering Guidelines
Issue 04 (2013-05-10)
8-14
WCDMA RAN
HSDPA
8 Engineering Guidelines
8. Run the NodeB MML command SET MACHSPARA. In this step, set Dynamic Code Switch to
OPEN(open).
9. Trace (DL)Hsdpa User Enhanced Schedule Data message, ucMaxPdschCodeNum is less than
the value of 5, it indicates the feature has been enabled, as shown in Figure 6-4.
Figure 8-4 Message Browser
Deactivation Procedure
1. Run the NodeB MML command SET MACHSPARA (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > Locell Algorithm Parameters > MAC
Parameters > MACHSPARA; CME batch modification center: Modifying Physical NodeB
Parameters in Batches). In this step, set Dynamic Code Switch to CLOSE(close).
Example
//Activation procedure
//Operations on the NodeB side
SET MACHSPARA: DYNCODESW=OPEN;
//Verification procedure
//Operations on the NodeB side
SET MACHSPARA: DYNCODESW=CLOSE;
//Operations on the BSC6900 side
MOD UCELLHSDPA: CellId=0, AllocCodeMode=Manual, HsPdschCodeNum=5;
//Operations on the NodeB side
SET MACHSPARA: DYNCODESW=OPEN;
//Deactivation procedure
//Operations on the NodeB side
SET MACHSPARA: DYNCODESW=CLOSE;
Issue 04 (2013-05-10)
8-15
WCDMA RAN
HSDPA
8 Engineering Guidelines
Prerequisites
Dependencies on Hardware
This
UE
License
This feature is not under license control.
Procedure
For details on how to activate, verify, and deactivate the WRFD-010611 HSDPA Enhanced Package
feature, see the following:
6.1 WRFD-01061112 HSDPA DRD in Directed Retry Decision Feature Parameter Description
Prerequisites
Dependencies on Hardware
This feature does not have any special requirements for hardware.
License
This feature is not under license control.
Issue 04 (2013-05-10)
8-16
WCDMA RAN
HSDPA
8 Engineering Guidelines
Procedure
Activation Procedure
Run the NodeB MML command SET MACHSPARA (CME single configuration: NodeB Configuration
Express > IUB_NodeB > Radio Layer > Locell Algorithm Parameters > MAC Parameters >
MACHSPARA; CME batch modification center: Modifying Physical NodeB Parameters in Batches). In
this step, set Scheduling Method to EPF(Enhanced PF).
Verification Procedure
Run the NodeB MML command LST MACHSPARA to check that Scheduling Method is set to EPF.
Deactivation Procedure
Run the NodeB MML command SET MACHSPARA (CME single configuration: NodeB Configuration
Express > IUB_NodeB > Radio Layer > Locell Algorithm Parameters > MAC Parameters >
MACHSPARA; CME batch modification center: Modifying Physical NodeB Parameters in Batches).
In this step, set Scheduling Method to an option other than EPF(Enhanced PF).
Example
//Activation procedure
SET MACHSPARA: SM=EPF;
//Verification procedure
LST MACHSPARA;
//Deactivation procedure
SET MACHSPARA: SM=PF;
Prerequisites
Dependencies on Hardware
The
BTS3812E and BTS3812AE must be configured with the EBBI, EBOI, EULP, and EULPd.
The
The
UEs
License
Issue 04 (2013-05-10)
8-17
WCDMA RAN
HSDPA
8 Engineering Guidelines
The license "96 HSDPA Users per Cell" on the BSC6900 side has been activated. For details about
how to activate the license, see License Management Feature Parameter Description.
Procedure
Activation Procedure
1. Run the BSC6900 MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS
Cell Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch
modification center: Modifying UMTS Cell Parameters in Batches). In this step, deselect the
HSDPA_UU_ADCTRL(HSDPA
UU
Load
Admission
Control
Algorithm)
and
HSUPA_UU_ADCTRL(HSUPA UU Load Admission Control Algorithm) check boxes under the
parameter Cell CAC algorithm switch, and select the DTX_DRX(Cell DTX_DRX Function Switch)
check box under the parameter Cell Hspa Plus function switch.
2. Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME single configuration: UMTS
Radio Global Configuration Express > Connection_Oriented RRM Switch Configuration >
Connection Oriented Algorithm Switches; CME batch modification center: Modifying RNC
Parameters
in
Batches)
to
deselect
DRA_HSDPA_STATE_TRANS_SWITCH
and
DRA_HSUPA_STATE_TRANS_SWITCH from the Dynamic Resource Allocation Switch list to
disable HSPA state transition.
3. Run the BSC6900 MML command SET UFRCCHLTYPEPARA (CME single configuration: UMTS
Radio Global Configuration Express > Basic Resource Control Parameter Configuration >
Channel Type Parameters; CME batch modification center: Modifying RNC Parameters in Batches)
to set Type of Channel Preferably Carrying Signaling RB to HSPA(UL_EDCH,DL_HSDSCH) and
Effective Flag of Signaling RB Channel Type to TRUE.
4. Run the BSC6900 MML command MOD UCELLHSUPA (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Configuration of HSUPA in Cell; CME batch
modification center: Modifying UMTS Cell Parameters in Batches) to set Code Number for E-AGCH
and Code Number for E-RGCH/E-HICH to appropriate values.
5. Run the BSC6900 MML command MOD UCELLCAC (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Oriented CAC Algorithm Parameters; CME
batch modification center: Modifying UMTS Cell Parameters in Batches) to stop reserving uplink and
downlink credit resources by setting UL handover credit reserved SF and DL handover credit and
code reserved SF to SFOFF(SFOFF), and setting Maximum HSDPA user number to 96.
Verification Procedure
1. On the BSC6900 LMT, click Monitor. Then, double-click Cell Performance Monitoring in the
Monitor Navigation Tree pane. In the displayed Cell Performance Monitoring dialog box, set
Monitor Item to Cell User Number.
2. Use UEs to access the cell successively and then establish PS services, for example, download files
through FTP.
Expected result: Each UE establishes PS services successfully.
If
the number of UEs is less than or equal to 96, uplink services are carried on HSUPA channels and
downlink services are carried on HSDPA channels.
If
the number of UEs is greater than 96, HSPA services of the excessive UEs are carried on R99
channels.
3. Check the maximum number of users through the counter VS.HSDPA.UE.Max.Cell on the M2000.
The 96 HSDPA users referred to in this feature are of the SRB Over HSPA type.
The 96 HSDPA UEs must support the CPC-DTX/DRX function.
Deactivation Procedure
This feature does not need to be deactivated.
Issue 04 (2013-05-10)
8-18
WCDMA RAN
HSDPA
8 Engineering Guidelines
Example
/*Activating 96 HSDPA Users per Cell*/
//Disabling the admission control function in an HSPA cell on the Uu interface and enabling the DTX-DRX
function
MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0,
HspaPlusSwitch=DTX_DRX-1;
//Disabling HSPA state transition
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0;
//Enabling SRB over HSPA
SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE;
//Allocating code resources to E-AGCHs and E-RGCHs
MOD UCELLHSUPA: CellId=111, EagchCodeNum=1, ErgchEhichCodeNum=5;
//Stop reserving uplink and downlink credit resources and setting the maximum number of HSDPA users to
96
MOD UCELLCAC: CellId=111, MaxHsdpaUserNum=96, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF;
Prerequisites
Dependencies on Hardware
The feature is available only for 3900 series base stations. 3900 series base stations (except
BTS3902E) must be configured with the WBBPd2 or WBBPd3. UEs must support the CPC-DTX/DRX.
License
The license "128 HSDPA Users per Cell" on the BSC6900 side has been activated. For details about
how to activate the license, see License Management Feature Parameter Description.
Procedure
Activation Procedure
1. Run the BSC6900 MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS
Cell Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch
modification center: Modifying UMTS Cell Parameters in Batches). In this step, deselect the
HSDPA_UU_ADCTRL(HSDPA
UU
Load
Admission
Control
Algorithm)
and
Issue 04 (2013-05-10)
8-19
WCDMA RAN
HSDPA
8 Engineering Guidelines
Verification Procedure
1. On the BSC6900 LMT, click Monitor. Then, double-click Cell Performance Monitoring in the
Monitor Navigation Tree pane. In the displayed Cell Performance Monitoring dialog box, set
Monitor Item to Cell User Number.
2. Use UEs to access the cell successively and then establish PS services, for example, download files
through FTP.
Expected result: Each UE establishes PS services successfully.
If
the number of UEs is less than or equal to 128, uplink services are carried on HSUPA channels and
downlink services are carried on HSDPA channels.
If
the number of UEs is greater than 128, HSPA services of the excessive UEs are carried on R99
channels.
3. Check the maximum number of users through the counter VS.HSDPA.UE.Max.Cell on the M2000.
The 128 HSDPA users referred to in this feature are of the SRB Over HSPA type.
The 128 HSDPA UEs must support the CPC-DTX/DRX.
Deactivation Procedure
This feature does not need to be deactivated.
Example
/*Activating 128 HSDPA Users per Cell*/
//Disabling the admission control function in an HSPA cell on the Uu interface and enabling the DTX-DRX
function
MOD UCELLALGOSWITCH: CellId=111, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0,
HspaPlusSwitch=DTX_DRX-1;
//Disabling HSPA state transition
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSDPA_STATE_TRANS_SWITCH-0&DRA_HSUPA_STATE_TRANS_SWITCH-0;
//Enabling SRB over HSPA
SET UFRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=TRUE;
//Allocating code resources to E-AGCHs and E-RGCHs
MOD UCELLHSUPA: CellId=111, EagchCodeNum=1, ErgchEhichCodeNum=7;
Issue 04 (2013-05-10)
8-20
WCDMA RAN
HSDPA
8 Engineering Guidelines
//Stop reserving uplink and downlink credit resources and setting the maximum number of HSDPA users to
128
MOD UCELLCAC: CellId=111, MaxHsdpaUserNum=128, UlHoCeResvSf=SFOFF, DlHoCeCodeResvSf=SFOFF;
Prerequisites
Dependencies on Hardware
The
BTS3812E and BTS3812AE are configured with the EBBI, EBOI, or EDLP board.
The
The
License
The
license controlling this feature has been activated. For details a how to activate the license, see
License Management Feature Parameter Description. For details about license items, see License
Management Feature Parameter Description.
Context
With this feature, the NodeB can dynamically select the optimum BLER target value based on the
channel quality fluctuation of HSDPA users. The NodeB then adjusts the Channel Quality Indicator (CQI)
accordingly, improving user throughput and cell throughput.
Procedure
Activation Procedure
Run the NodeB MML command SET MACHSPARA (CME single configuration: Introduction to the
Configuration Express for Iub Interfaces; CME batch modification center: Modifying Physical NodeB
Parameters in Batches). In this step, set CQI Adjust Algorithm Switch of non-Conversational
Service to CQI_ADJ_BY_DYN_BLER(CQI Adjusted by Dynamic BLER).
Verification Procedure
Run the NodeB MML command LST MACHSPARA. In this step, check that CQI Adjust Algorithm
Switch of non-Conversational Service is set to CQI_ADJ_BY_DYN_BLER.
Issue 04 (2013-05-10)
8-21
WCDMA RAN
HSDPA
8 Engineering Guidelines
Deactivation Procedure
Run the NodeB MML command SET MACHSPARA (CME single configuration: Introduction to the
Configuration Express for Iub Interfaces; CME batch modification center: Modifying Physical NodeB
Parameters in Batches). In this step, set CQI Adjust Algorithm Switch of non-Conversational
Service to NO_CQI_ADJ(Not CQI Adjust Algorithm).
----End
Example
//Activating CQI Adjustment Based on Dynamic BLER Target
SET MACHSPARA: LOCELL=0, CQIADJALGOFNONCON=CQI_ADJ_BY_DYN_BLER;
//Verifying CQI Adjustment Based on Dynamic BLER Target
LST MACHSPARA: LOCELL=0;
//Deactivating CQI Adjustment Based on Dynamic BLER Target
SET MACHSPARA: CQIADJALGOFNONCON=NO_CQI_ADJ;
VS.DataOutput.Mean: a NodeB counter that measures the average cell throughput at the
MAC-hs/MAC-ehs layer within a measurement period
The values of the preceding counters increase after this feature is activated. Note that gains brought by
this feature vary in different scenarios.
Prerequisites
3900 series base stations support this feature. To support this feature, the 3900 series base
stations must be configured with the WBBPb, WBBPd or WBBPf board.
All
DBS3800 series base stations support this feature. To support this feature, the DBS3800 series
base stations must be configured with the EBBC or EBBCd board.
The
Issue 04 (2013-05-10)
8-22
WCDMA RAN
HSDPA
8 Engineering Guidelines
WRFD-010610
WRFD-010611
License
The license controlling this feature has been activated. For details about the license items and how to
activate the license, see License Management Feature Parameter Description.
Others Prerequisites
As
recommended, GBRs have been configured on the RNC for all BE services.
Context
Developed on the basis of the EPF algorithm, this feature considers UE locations as the criterion for
adjusting HSDPA scheduling weights. This feature gives more scheduling opportunities to UEs close
to the NodeB and increases the cell throughput on the downlink.
Precautions
With
this feature, HSDPA UEs at cell edges have fewer scheduling opportunities and the cell
throughput at cell edges drops. If GBRs are not configured for BE services, HSDPA UEs at cell edges
may have to wait a long time before they can get scheduling opportunities. As a result, traffic radio
bearers (TRBs) are more likely to reset and the call drop rate increases. The magnitude of this impact
depends on factors such as UE location distribution and service distribution in the cell. It is
recommended that GBRs be configured for BE services to ensure network performance.
Procedure
Activation Procedure
Run the NodeB MML command SET MACHSPARA (CME single configuration: Introduction to the
Configuration Express for Iub Interfaces; CME batch modification center: Modifying Physical NodeB
Parameters in Batches). In this step, set Scheduling Method to EPF_LOC(Location based EPF) and
set Location Weight.
Verification Procedure
Run the NodeB MML command LST MACHSPARA. If the command output shows that the value of
Scheduling Method is EPF_LOC(Location based EPF), this feature has been activated for the cell.
Deactivation Procedure
Run the NodeB MML command SET MACHSPARA (CME single configuration: introduction to the
Configuration Express for Iub Interfaces; CME batch modification center: Modifying Physical NodeB
Parameters in Batches). In this step, set Scheduling Method to a value except EPF_LOC(Location
based EPF).
----End
Example
//Activation procedure
SET MACHSPARA: LOCELL=1, SM=EPF_LOC, LOCWEIGHT=1;
//Deactivation procedure
SET MACHSPARA: LOCELL=1, SM=EPF;
Issue 04 (2013-05-10)
8-23
WCDMA RAN
HSDPA
8 Engineering Guidelines
measurement period
VS.DataTtiRatio.Mean:
ratio of the time when at least one HSDPA user has data to transmit in the
queue buffer within a measurement period
VS.HSDPA.InactiveDataTtiRatio.Mean:
average ratio of the time when at least one HSDPA user has
data to transmit in the buffer but no HSDPA user transmits data at the physical layer within a
measurement period
Step 2 Verify whether the value of the cell throughput of HSDPA is greater after this feature is activated.
How much the value of cell throughput of HSDPA increase depends on factors such as UE distribution
and the service model.
This feature applies to the scenario of continuous downlink data transmission, it cannot show gains if
there is no insufficient data sources.
Parameter Optimization
After the EPF_LOC scheduling algorithm is enabled, the value of the LOCWEIGHT parameter affects
the cell throughput and the degree to which UEs are differentiated from each other. A larger value for this
parameter means that UE locations weigh more in scheduling. This gives more scheduling opportunities
to UEs closer to the NodeB, increases the cell throughput, and decreases the throughput at cell edges.
In this case, to ensure equity among UEs, set the LOCWEIGHT parameter to a small value; to maximize
the cell throughput while ensuring a GBR for UEs at cell edges, set the LOCWEIGHT parameter to a
large value.
When the value of the VS.DataTtiRatio.Mean counter for a cell is greater than 50%, for example, in
densely populated urban areas, the HSDPA remaining power appending algorithm may decrease the
CQI and cell throughput. Under this condition, the RESVERD3 parameter should be set to a value
equal to or less than 4.
Issue 04 (2013-05-10)
8-24
WCDMA RAN
HSDPA
8 Engineering Guidelines
When the value of the VS.DataTtiRatio.Mean counter for a cell is less than 10%, for example, in
suburban areas, the RESVERD3 parameter can be set to a comparatively large value, for example, 12
(equal to 3 dB), to improve user experience.
Network KPIs
CS
PS
CS
PS
RNC counter
VS.MeanTCP
NodeB counters
VS.AckTotal
VS.NackTotal
VS.DtxTotal
VS.DataTtiRatio.Mean
Dependencies on Hardware
None.
License
None.
Procedure
Activation Procedure
Run the NodeB MML command SET LOCELLRSVP to set RESVERD3 to a non-zero value.
Verification Procedure
Check the value of the RNC counter VS.MeanTCP for the following results:
The
value of this counter is less than 80% before this algorithm is enabled.
The
value of this counter is increased by a value less than the value specified by the RESVERD3
parameter after this algorithm is enabled.
Issue 04 (2013-05-10)
8-25
WCDMA RAN
HSDPA
8 Engineering Guidelines
Deactivation Procedure
Run the NodeB MML command SET LOCELLRSVP to set RESVERD3 to 0.
Example
//Activation procedure
SET LOCELLRSVP: LOCELL=1, RESVERD3=1;
//Deactivation procedure
SET LOCELLRSVP: LOCELL=1, RESVERD3=0;
VS.AckTotal
VS.NackTotal
VS.DtxTotal
VS.DataOutput.Mean
VS.DataTtiRatio.Mean
VS.HSDPA.InactiveDataTtiRatio.Mean
Prerequisites
Dependencies on Hardware
None
Issue 04 (2013-05-10)
8-26
WCDMA RAN
HSDPA
8 Engineering Guidelines
License
None
Procedure
Activation Procedure
Run the NodeB MML command SET LOCELLRSVP with RESVERD1:RSVDBIT29 set to 1.
Verification Procedure
Step 1 Check the values of the NodeB counters: VS.AckTotal, VS.NackTotal, and VS.DtxTotal.
Step 2 Use the following formula to obtain the BLER of HSDPA burst services before and after function
enabling:
BLER = (VS.NackTotal + VS.DtxTotal)/(VS.AckTotal +VS.NackTotal + VS.DtxTotal)
If the BLER decreases after function enabling, the function has taken effect. Otherwise, the function
does not take effect yet.
Step 3 Use the following formula to obtain the cell throughput before and after function enabling:
Cell throughput = VS.DataOutput.Mean/(VS.DataTtiRatio.Mean VS.HSDPA.InactiveDataTtiRatio.Mean)
If the cell throughput increases after function enabling, the function has taken effect. Otherwise, the
function does not take effect yet.
----End
Deactivation Procedure
Run the NodeB MML command SET LOCELLRSVP with RESVERD1:RSVDBIT29 set to 1.
Example
//Enabling BLER Optimization for HSDPA Burst Services
SET LOCELLRSVP: RESVERD1=RSVDBIT29-1;
Issue 04 (2013-05-10)
8-27
WCDMA RAN
HSDPA
9 Parameters
9 Parameters
Table 9-1 Parameter description
Parameter NE
ID
MML
Command
Feature ID Feature
Name
Description
Issue 04 (2013-05-10)
9-1
WCDMA RAN
HSDPA
Parameter NE
ID
9 Parameters
MML
Command
Feature ID Feature
Name
200
Description
Configuration
Control
(DCCC)
HCS
(Hierarchical
Cell
Structure)
HSDPA
Meaning:This parameter specifies code
Static Code reshuffling switch for HDSPA. If the switch
Allocation
is set as ON, codes occupied by the R99
and
service can be adjusted toward codes with
RNC-Controll small numbers to release the sharing
ed Dynamic codes adjacent to HSDPA code. When "
Code
Allocate Code Mode " is set to Automatic
Allocation
or the NodeB automatic code algorithm is
enabled, the released codes can be used
by HSDPA and thus HSDPA throughput
can be improved.
GUI Value Range:OFF(OFF), ON(ON)
Actual Value Range:OFF, ON
Unit:None
Default Value:ON(ON)
HSDPA
Meaning:H-based code tree reshuffle user
Static Code number threshold. When the switch "Code
Allocation
Adjust Switch for HSDPA"is enabled, if the
and
number of users on the tree to be
RNC-Controll reshuffled is no greater than this
ed Dynamic parameter, the reshuffle is allowed.
Code
Otherwise, the reshuffle is given up. This
Allocation
parameter limits the number of users
involved in one reshuffle so that reshuffle
on lots of users at a time is avoided.
GUI Value Range:1~16
Actual Value Range:1~16
Unit:None
Default Value:3
Issue 04 (2013-05-10)
9-2
WCDMA RAN
HSDPA
Parameter NE
ID
9 Parameters
MML
Command
Feature ID Feature
Name
Description
non-conversational services based on the
fixed IBLER. The IBLER will converge to
this target value.
GUI Value Range:NO_CQI_ADJ(Not CQI
Adjust Algorithm),
CQI_ADJ_BY_IBLER(CQI Adjusted by
IBLER), CQI_ADJ_BY_DYN_BLER(CQI
Adjusted by Dynamic BLER)
Actual Value Range:NO_CQI_ADJ,
CQI_ADJ_BY_IBLER,
CQI_ADJ_BY_DYN_BLER
Unit:None
Default Value:NO_CQI_ADJ(Not CQI
Adjust Algorithm)
HappyBR
BSC69 SET
WRFD-010 HSDPA Flow Meaning:Defines the happy bit rate of the
00
UUSERHAPP 61010
Control
best effort (BE) service with different user
YBR
priorities(user priorities can be set by
parameter UserPriority). This Happy bit
rate is sent to NodeB by RNC through the
Iub interface. When the NodeB resource is
limited and the HS-DSCH bit rate of the
user exceeds the Happy bit rate, the
HS-DSCH scheduling priority will be
decreased. When this parameter is set to
zero, it indicates that NodeB will not adjust
the HS-DSCH scheduling priority. This
value of parameter can be set by the
HappyBR in command ADD
UOPERUSERHAPPYBR. If the value of
the parameter HappyBR in command ADD
UOPERUSERHAPPYBR is larger than
5000, it will be set to the minimum of the
HappyBR value in SET UUSERHAPPYBR
and 5000.
Issue 04 (2013-05-10)
9-3
WCDMA RAN
HSDPA
Parameter NE
ID
9 Parameters
MML
Command
Feature ID Feature
Name
Description
GUI Value Range:0~27900
Actual Value Range:0~27900
Unit:kbit/s
Default Value:0
Issue 04 (2013-05-10)
9-4
WCDMA RAN
HSDPA
Parameter NE
ID
9 Parameters
MML
Command
Feature ID Feature
Name
Description
"Code Max Number for HS-PDSCH".
GUI Value Range:1~15
Actual Value Range:1~15
Unit:None
Default Value:5
HSDPA
Meaning:This parameter named Measure
Introduction Power Offset Constant is used to compute
Package
measurement power offset. Measurement
power offset is used by UE to obtain total
HSDPA
received HS-PDSCH power. The
Power
calculation for Measure Power Offset is as
Control
shown below:
Measure Power Offset = Max(-6,
Min(13,CellMaxPower - PcpichPower Measure Power OffsetConstant)). For
details of the IE "Measure Power Offset",
refer to 3GPP TS 25.214.
GUI Value Range:Minus3.0DB(-3.0dB),
Minus2.5DB(-2.5dB),
Minus2.0DB(-2.0dB),
Minus1.5DB(-1.5dB),
Minus1.0DB(-1.0dB),
Minus0.5DB(-0.5dB), 0.0DB(0.0dB),
Issue 04 (2013-05-10)
9-5
WCDMA RAN
HSDPA
Parameter NE
ID
9 Parameters
MML
Command
Feature ID Feature
Name
Description
0.5DB(0.5dB), 1.0DB(1.0dB),
1.5DB(1.5dB), 2.0DB(2.0dB),
2.5DB(2.5dB), 3.0DB(3.0dB),
3.5DB(3.5dB), 4.0DB(4.0dB),
4.5DB(4.5dB), 5.0DB(5.0dB),
5.5DB(5.5dB), 6.0DB(6.0dB),
6.5DB(6.5dB), 7.0DB(7.0dB),
7.5DB(7.5dB), 8.0DB(8.0dB),
8.5DB(8.5dB), 9.0DB(9.0dB),
9.5DB(9.5dB), 10.0DB(10.0dB),
10.5DB(10.5dB), 11.0DB(11.0dB),
11.5DB(11.5dB), 12.0DB(12.0dB),
12.5DB(12.5dB), 13.0DB(13.0dB),
13.5DB(13.5dB), 14.0DB(14.0dB),
14.5DB(14.5dB), 15.0DB(15.0dB),
15.5DB(15.5dB), 16.0DB(16.0dB),
16.5DB(16.5dB), 17.0DB(17.0dB),
17.5DB(17.5dB), 18.0DB(18.0dB),
18.5DB(18.5dB), 19.0DB(19.0dB)
Actual Value Range:-3.0, -2.5, -2.0, -1.5,
-1.0, -0.5, 0.0, 0.5, 1.0, 1.5, 2.0, 2.5, 3.0,
3.5, 4.0, 4.5, 5.0, 5.5, 6.0, 6.5, 7.0, 7.5,
8.0, 8.5, 9.0, 9.5, 10.0, 10.5, 11.0, 11.5,
12.0, 12.5, 13.0, 13.5, 14.0, 14.5, 15.0,
15.5, 16.0, 16.5, 17.0, 17.5, 18.0, 18.5,
19.0
Unit:dB
Default Value:2.5DB(2.5dB)
Issue 04 (2013-05-10)
9-6
WCDMA RAN
HSDPA
Parameter NE
ID
9 Parameters
MML
Command
Feature ID Feature
Name
Description
Actual Value Range:0, 1, 2, 3
Unit:None
Default Value:1
None
RESVERD NodeB SET
1
LOCELLRSVP
None
Issue 04 (2013-05-10)
9-7
WCDMA RAN
HSDPA
Parameter NE
ID
9 Parameters
MML
Command
Feature ID Feature
Name
Description
RSVDBIT3(Reserved Switch 3),
RSVDBIT4(Reserved Switch 4),
RSVDBIT5(Reserved Switch 5),
RSVDBIT6(Reserved Switch 6),
RSVDBIT7(Reserved Switch 7),
RSVDBIT8(Reserved Switch 8),
RSVDBIT9(Reserved Switch 9),
RSVDBIT10(Reserved Switch 10),
RSVDBIT11(Reserved Switch 11),
RSVDBIT12(Reserved Switch 12),
RSVDBIT13(Reserved Switch 13),
RSVDBIT14(Reserved Switch 14),
RSVDBIT15(Reserved Switch 15),
RSVDBIT16(Reserved Switch 16),
RSVDBIT17(Reserved Switch 17),
RSVDBIT18(Reserved Switch 18),
RSVDBIT19(Reserved Switch 19),
RSVDBIT20(Reserved Switch 20),
RSVDBIT21(Reserved Switch 21),
RSVDBIT22(Reserved Switch 22),
RSVDBIT23(Reserved Switch 23),
RSVDBIT24(Reserved Switch 24),
RSVDBIT25(Reserved Switch 25),
RSVDBIT26(Reserved Switch 26),
RSVDBIT27(Reserved Switch 27),
RSVDBIT28(Reserved Switch 28),
RSVDBIT29(Reserved Switch 29),
RSVDBIT30(Reserved Switch 30),
RSVDBIT31(Reserved Switch 31),
RSVDBIT32(Reserved Switch 32)
Actual Value Range:RSVDBIT1,
RSVDBIT2, RSVDBIT3, RSVDBIT4,
RSVDBIT5, RSVDBIT6, RSVDBIT7,
RSVDBIT8, RSVDBIT9, RSVDBIT10,
RSVDBIT11, RSVDBIT12, RSVDBIT13,
RSVDBIT14, RSVDBIT15, RSVDBIT16,
RSVDBIT17, RSVDBIT18, RSVDBIT19,
RSVDBIT20, RSVDBIT21, RSVDBIT22,
RSVDBIT23, RSVDBIT24, RSVDBIT25,
RSVDBIT26, RSVDBIT27, RSVDBIT28,
RSVDBIT29, RSVDBIT30, RSVDBIT31,
RSVDBIT32
Unit:None
Default Value:Reserved Switch 1:OFF,
Reserved Switch 2:OFF, Reserved Switch
3:OFF, Reserved Switch 4:OFF, Reserved
Switch 5:OFF, Reserved Switch 6:OFF,
Reserved Switch 7:OFF, Reserved Switch
8:OFF, Reserved Switch 9:OFF, Reserved
Switch 10:OFF, Reserved Switch 11:OFF,
Issue 04 (2013-05-10)
9-8
WCDMA RAN
HSDPA
Parameter NE
ID
9 Parameters
MML
Command
Feature ID Feature
Name
Description
Reserved Switch 12:OFF, Reserved
Switch 13:OFF, Reserved Switch 14:OFF,
Reserved Switch 15:OFF, Reserved
Switch 16:OFF, Reserved Switch 17:OFF,
Reserved Switch 18:OFF, Reserved
Switch 19:OFF, Reserved Switch 20:OFF,
Reserved Switch 21:OFF, Reserved
Switch 22:OFF, Reserved Switch 23:OFF,
Reserved Switch 24:OFF, Reserved
Switch 25:OFF, Reserved Switch 26:OFF,
Reserved Switch 27:OFF, Reserved
Switch 28:OFF, Reserved Switch 29:OFF,
Reserved Switch 30:OFF, Reserved
Switch 31:OFF, Reserved Switch 32:OFF
None
RESVERD NodeB SET
3
LOCELLRSVP
None
Issue 04 (2013-05-10)
9-9
WCDMA RAN
HSDPA
Parameter NE
ID
9 Parameters
MML
Command
Feature ID Feature
Name
Description
POWER_PRI, POWERCODE_BAL
Unit:None
Default
Value:POWERCODE_BAL(Balance
between Code and Power)
Meaning:Reserved parameter 1.
Disuse statement: This parameter is used
temporarily in patch versions and will be
replaced with a new parameter in later
versions. The new parameter ID reflects
the parameter function. Therefore, this
parameter is not recommended for the
configuration interface.
GUI Value Range:RSVDBIT1(Reserved
Switch 1), RSVDBIT2(Reserved Switch 2),
RSVDBIT3(Reserved Switch 3),
RSVDBIT4(Reserved Switch 4),
RSVDBIT5(Reserved Switch 5),
RSVDBIT6(Reserved Switch 6),
RSVDBIT7(Reserved Switch 7),
RSVDBIT8(Reserved Switch 8),
RSVDBIT9(Reserved Switch 9),
RSVDBIT10(Reserved Switch 10),
RSVDBIT11(Reserved Switch 11),
RSVDBIT12(Reserved Switch 12),
RSVDBIT13(Reserved Switch 13),
RSVDBIT14(Reserved Switch 14),
RSVDBIT15(Reserved Switch 15),
RSVDBIT16(Reserved Switch 16)
Actual Value Range:RSVDBIT1,
RSVDBIT2, RSVDBIT3, RSVDBIT4,
RSVDBIT5, RSVDBIT6, RSVDBIT7,
Issue 04 (2013-05-10)
9-10
WCDMA RAN
HSDPA
Parameter NE
ID
9 Parameters
MML
Command
Feature ID Feature
Name
Description
RSVDBIT8, RSVDBIT9, RSVDBIT10,
RSVDBIT11, RSVDBIT12, RSVDBIT13,
RSVDBIT14, RSVDBIT15, RSVDBIT16
Unit:None
Default
Value:RSVDBIT1-0&RSVDBIT2-0&RSVD
BIT3-0&RSVDBIT4-0&RSVDBIT5-0&RSV
DBIT6-0&RSVDBIT7-0&RSVDBIT8-0&RS
VDBIT9-0&RSVDBIT10-0&RSVDBIT11-0
&RSVDBIT12-0&RSVDBIT13-0&RSVDBI
T14-0&RSVDBIT15-0&RSVDBIT16-0
SM
NodeB SET
WRFD-010 HSDPA
MACHSPARA 61009
H-ARQ &
Scheduling
(MAX C/I,
RR and PF)
SPI
BSC69 SET
WRFD-020 Differentiated Meaning:Scheduling priority of interactive
00
USPIWEIGHT 806
Service
and background services. Value 11
Based on
indicates the highest priority, while value 2
SPI Weight indicates the lowest priority. Values 0, 1,
12, 13, 14, and 15 are reserved for the
other services.
GUI Value Range:0~15
Actual Value Range:0~15
Unit:None
Issue 04 (2013-05-10)
9-11
WCDMA RAN
HSDPA
Parameter NE
ID
9 Parameters
MML
Command
Feature ID Feature
Name
Description
Default Value:None
Issue 04 (2013-05-10)
9-12
WCDMA RAN
HSDPA
10 Counters
10 Counters
Table 10-1 Counter description
Count Counter Name
er ID
Counter
Description
503316 VS.AckTotal
54
503316 VS.NackTotal
55
503316 VS.DtxTotal
56
503316 VS.AckFirst
57
503316 VS.AckRetrans.1
58
503316 VS.AckRetrans.2
59
HSDPA
H-ARQ &
Scheduling
(MAX C/I,
RR and PF)
503316 VS.AckRetrans.3
60
HSDPA
H-ARQ &
Scheduling
(MAX C/I,
RR and PF)
Issue 04 (2013-05-10)
NE
Feature ID
Feature
Name
HSDPA
H-ARQ &
Scheduling
(MAX C/I,
RR and PF)
10-1
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503316 VS.AckRetrans.4
61
503316 VS.AckRetrans.5
62
503316 VS.AckRetrans.6
63
503316 VS.AckRetrans.7
64
503316 VS.AckRetrans.8
65
503316 VS.AckRetrans.9
66
503316 VS.AckRetrans.10
67
503316 VS.AckRemain
68
Issue 04 (2013-05-10)
NE
Feature ID
Feature
Name
HSDPA
H-ARQ &
Scheduling
(MAX C/I,
RR and PF)
10-2
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503317 VS.HSDPA.MIMO64QAMCfg.ActedNum
17
NE
Feature ID
Feature
Name
HSDPA
Introduction
Package
HSPA+
Downlink
42Mbps per
User
DL
64QAM+MI
MO
503317 VS.HSDPA.MIMO64QAMCfg.ScheduledNu Number of times NodeB WRFD-0106
18
m
that all the users
10
configured in
64QAM+MIMO
mode in a cell
WRFD-0106
are scheduled
89
during the
measurement
period
WRFD-0106
93
HSDPA
Introduction
Package
HSPA+
Downlink
42Mbps per
User
DL
64QAM+MI
MO
503317 VS.HSDPA.DCCfg.AnchorCarrierActedNum Number of times NodeB
19
that all the users
configured in DC
mode in a cell
are scheduled by
AnchorCarrier
during the
measurement
period
WRFD-0106 HSDPA
10
Introduction
Package
WRFD-0106
89
HSPA+
Downlink
42Mbps per
WRFD-0106 User
96
DC-HSDPA
503317 VS.HSDPA.DCCfg.SupCarrierActedNum
20
Issue 04 (2013-05-10)
10-3
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
carrier
Feature ID
Feature
Name
89
HSPA+
Downlink
42Mbps per
WRFD-0106 User
96
DC-HSDPA
503317 VS.HSDPA.DCCfg.DualCarrierActedNum
21
WRFD-0106 HSDPA
10
Introduction
Package
WRFD-0106
89
HSPA+
Downlink
42Mbps per
WRFD-0106 User
96
DC-HSDPA
503317 VS.HSDPA.16QAMCfg.ActedNum
22
503317 VS.HSDPA.QPSKCfg.ActedNum
23
HSDPA
Introduction
Package
DL 16QAM
Modulation
503317 VS.HSDPA.All.ScheduledNum
24
Issue 04 (2013-05-10)
HSDPA
Introduction
Package
HSDPA
H-ARQ &
Scheduling
(MAX C/I,
RR and PF)
10-4
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503317 VS.UsedCQI0
54
NE
Feature ID
Feature
Name
WRFD-0106
1018
Time and
HS-PDSCH
Codes
WRFD-0106 Multiplex
1019
HSDPA
Dynamic
Power
Allocation
503317 VS.UsedCQI1
55
503317 VS.UsedCQI2
56
Issue 04 (2013-05-10)
10-5
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503317 VS.UsedCQI3
57
NE
Feature ID
Feature
Name
WRFD-0106
1018
Time and
HS-PDSCH
Codes
WRFD-0106 Multiplex
1019
HSDPA
Dynamic
Power
Allocation
503317 VS.UsedCQI4
58
503317 VS.UsedCQI5
59
Issue 04 (2013-05-10)
10-6
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503317 VS.UsedCQI6
60
NE
Feature ID
Feature
Name
WRFD-0106
1018
Time and
HS-PDSCH
Codes
WRFD-0106 Multiplex
1019
HSDPA
Dynamic
Power
Allocation
503317 VS.UsedCQI7
61
503317 VS.UsedCQI8
62
Issue 04 (2013-05-10)
10-7
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503317 VS.UsedCQI9
63
NE
Feature ID
Feature
Name
WRFD-0106
1018
Time and
HS-PDSCH
Codes
WRFD-0106 Multiplex
1019
HSDPA
Dynamic
Power
Allocation
503317 VS.UsedCQI10
64
503317 VS.UsedCQI11
65
Issue 04 (2013-05-10)
10-8
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503317 VS.UsedCQI12
66
NE
Feature ID
Feature
Name
WRFD-0106
1018
Time and
HS-PDSCH
Codes
WRFD-0106 Multiplex
1019
HSDPA
Dynamic
Power
Allocation
503317 VS.UsedCQI13
67
503317 VS.UsedCQI14
68
Issue 04 (2013-05-10)
10-9
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503317 VS.UsedCQI15
69
NE
Feature ID
Feature
Name
WRFD-0106
1018
Time and
HS-PDSCH
Codes
WRFD-0106 Multiplex
1019
HSDPA
Dynamic
Power
Allocation
503317 VS.UsedCQI16
70
503317 VS.UsedCQI17
71
Issue 04 (2013-05-10)
10-10
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503317 VS.UsedCQI18
72
NE
Feature ID
Feature
Name
WRFD-0106
1018
Time and
HS-PDSCH
Codes
WRFD-0106 Multiplex
1019
HSDPA
Dynamic
Power
Allocation
503317 VS.UsedCQI19
73
503317 VS.UsedCQI20
74
Issue 04 (2013-05-10)
10-11
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503317 VS.UsedCQI21
75
NE
Feature ID
Feature
Name
WRFD-0106
1018
Time and
HS-PDSCH
Codes
WRFD-0106 Multiplex
1019
HSDPA
Dynamic
Power
Allocation
503317 VS.UsedCQI22
76
503317 VS.UsedCQI23
77
Issue 04 (2013-05-10)
10-12
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503317 VS.UsedCQI24
78
NE
Feature ID
Feature
Name
WRFD-0106
1018
Time and
HS-PDSCH
Codes
WRFD-0106 Multiplex
1019
HSDPA
Dynamic
Power
Allocation
503317 VS.UsedCQI25
79
503317 VS.UsedCQI26
80
Issue 04 (2013-05-10)
10-13
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503317 VS.UsedCQI27
81
NE
Feature ID
Feature
Name
WRFD-0106
1018
Time and
HS-PDSCH
Codes
WRFD-0106 Multiplex
1019
HSDPA
Dynamic
Power
Allocation
503317 VS.UsedCQI28
82
503317 VS.UsedCQI29
83
Issue 04 (2013-05-10)
10-14
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503317 VS.UsedCQI30
84
NE
Feature ID
Feature
Name
WRFD-0106
1018
Time and
HS-PDSCH
Codes
WRFD-0106 Multiplex
1019
HSDPA
Dynamic
Power
Allocation
503317 VS.UsedCQI31to39
85
HSDPA
Introduction
Package
Time and
HS-PDSCH
Codes
WRFD-0106 Multiplex
1019
HSDPA
Dynamic
Power
Allocation
503318 VS.HSDPA.DataOutput.TRB
38
503318 VS.HSDPA.DataTtiNum.TRB
39
503318 VS.HSDPA.InactiveDataTtiNum.TRB
40
Issue 04 (2013-05-10)
10-15
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
no HSDPA user
transmits data at
the physical layer
503327 VS.IUB.FlowCtrol.DL.AdjBW.LgcPort1.Max IUB logic port_1 NodeB WRFD-0106 HSDPA
24
maximum DL
1010
Flow
HSDPA available
Control
bandwidth
503327 VS.IUB.FlowCtrol.DL.AdjBW.LgcPort1.Min IUB logic port_1 NodeB WRFD-0106 HSDPA
25
minimum DL
1010
Flow
HSDPA available
Control
bandwidth
503327 VS.IUB.FlowCtrol.DL.AdjBW.LgcPort1.Avg IUB logic port_1 NodeB WRFD-0106 HSDPA
26
average DL
1010
Flow
HSDPA available
Control
bandwidth
503327 VS.IUB.FlowCtrol.DL.Delay.UpBW.Num.Lgc IUB logic port_1 NodeB WRFD-0106 HSDPA
28
Port1
DL HSDPA
1010
Flow
available
Control
bandwidth
increase times
after jitter
congestion
released
503327 VS.IUB.FlowCtrol.DL.Drop.UpBW.Num.Lgc IUB logic port_1 NodeB WRFD-0106 HSDPA
29
Port1
DL HSDPA
1010
Flow
available
Control
bandwidth
increase times
after packet loss
congestion
released
503327 VS.IUB.FlowCtrol.DL.DelayCong.DownBW IUB logic port_1 NodeB WRFD-0106 HSDPA
31
Num.LgcPort1
DL HSDPA
1010
Flow
available
Control
bandwidth
decrease times
for jitter
congestion
503327 VS.IUB.FlowCtrol.DL.DropCong.DownBWN IUB logic port_1 NodeB WRFD-0106 HSDPA
33
um.LgcPort1
DL HSDPA
1010
Flow
available
Control
bandwidth
decrease times
Issue 04 (2013-05-10)
10-16
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
Issue 04 (2013-05-10)
10-17
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
Issue 04 (2013-05-10)
10-18
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
503416 VS.ScchCodeUtil.Mean
48
Dynamic
Code
Allocation
Based on
Node B
503416 VS.ScchCodeUtil.Max
49
Issue 04 (2013-05-10)
10-19
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
Multiplex
WRFD-0106
1005
HSDPA
Static Code
Allocation
WRFD-0106 and
31
RNC-Contr
olled
Dynamic
Code
Allocation
Dynamic
Code
Allocation
Based on
Node B
503416 VS.ScchCodeUtil.Min
50
Dynamic
Code
Allocation
Based on
Node B
503416 VS.PdschCodeUtil.Mean
51
Issue 04 (2013-05-10)
10-20
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
in a cell
WRFD-0106 Time and
1018
HS-PDSCH
Codes
Multiplex
WRFD-0106
1005
HSDPA
Static Code
WRFD-0106 Allocation
and
31
RNC-Contr
olled
Dynamic
Code
Allocation
Dynamic
Code
Allocation
Based on
Node B
503416 VS.PdschCodeUtil.Max
52
Dynamic
Code
Allocation
Based on
Issue 04 (2013-05-10)
10-21
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
Node B
503416 VS.PdschCodeUtil.Min
53
Dynamic
Code
Allocation
Based on
Node B
503416 VS.ScchCodeUtil.Mean.User
54
15 Codes
per Cell
Time and
HS-PDSCH
Codes
Multiplex
WRFD-0106
1005
HSDPA
Static Code
WRFD-0106 Allocation
and
31
RNC-Contr
olled
Dynamic
Code
Allocation
Issue 04 (2013-05-10)
10-22
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
Dynamic
Code
Allocation
Based on
Node B
503416 VS.ScchCodeUtil.Mean.Data
55
WRFD-0106 15 Codes
1001
per Cell
Dynamic
Code
Allocation
Based on
Node B
503416 VS.PdschCodeUtil.Mean.User
56
15 Codes
per Cell
Time and
HS-PDSCH
Codes
Multiplex
WRFD-0106
1005
HSDPA
Static Code
WRFD-0106 Allocation
and
31
RNC-Contr
olled
Dynamic
Issue 04 (2013-05-10)
10-23
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
Code
Allocation
Dynamic
Code
Allocation
Based on
Node B
503416 VS.PdschCodeUtil.Mean.Data
57
WRFD-0106 15 Codes
1001
per Cell
Dynamic
Code
Allocation
Based on
Node B
503416 VS.UserTtiRatio.Mean
58
503416 VS.DataTtiRatio.Mean
59
Issue 04 (2013-05-10)
10-24
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503416 VS.RabNum.Mean
60
503416 VS.RabNum.Max
61
503416 VS.RabNum.Min
62
503416 VS.DataRabNum.Mean
63
503416 VS.DataRabNum.Max
64
503416 VS.DataRabNum.Min
65
503416 VS.RabNumAve.User
66
503416 VS.RabNumAve.UserData
67
Issue 04 (2013-05-10)
NE
Feature ID
Feature
Name
10-25
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
503416 VS.DataOutput.Max
69
503416 VS.DataOutput.Min
70
503416 VS.DataOutput.User
71
503416 VS.DataOutput.UserData
72
503416 VS.DataOutput.Rab
73
503416 VS.DataOutput.RabData
74
Issue 04 (2013-05-10)
10-26
WCDMA RAN
HSDPA
10 Counters
Counter
Description
503416 VS.ScchPwrRatio.Mean
75
NE
Feature ID
Feature
Name
WRFD-0106
1019
HSDPA
Dynamic
Power
Allocation
503416 VS.ScchPwrRatio.Max
76
503416 VS.ScchPwrRatio.Min
77
503416 VS.PdschPwrRatio.Mean
78
Maximum
transmit power
over the
HS-SCCH in a
cell
Minimum
transmit power
over the
HS-SCCH in a
cell
WRFD-0106
1019
HSDPA
Dynamic
Power
Allocation
WRFD-0106
1019
HSDPA
Dynamic
Power
Allocation
503416 VS.PdschPwrRatio.Max
79
Issue 04 (2013-05-10)
NodeB WRFD-0106
Maximum
transmit power
1004
over the
HS-PDSCH in a
cell
WRFD-0106
1019
HSDPA
Power
Control
HSDPA
Dynamic
Power
10-27
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
Allocation
503416 VS.PdschPwrRatio.Min
80
NodeB WRFD-0106
Minimum
transmit power
1004
over the
HS-PDSCH in a
cell
WRFD-0106
1019
HSDPA
Power
Control
HSDPA
Dynamic
Power
Allocation
503416 VS.ScchPwrRatio.User
81
503416 VS.PdschPwrRatio.User
82
WRFD-0106 HSDPA
1004
Power
Control
WRFD-0106 HSDPA
1004
Power
Control
WRFD-0106 HSDPA
1004
Power
Control
503416 VS.ScchPwrRatio.UserData
83
503416 VS.PdschPwrRatio.Data
84
Issue 04 (2013-05-10)
WRFD-0106
1019
HSDPA
Dynamic
Power
Allocation
WRFD-0106
1019
HSDPA
Dynamic
Power
Allocation
WRFD-0106
1019
HSDPA
Dynamic
10-28
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
queue buffer
503416 VS.DataDiscardRatio.Mean
85
Feature ID
Feature
Name
Power
Allocation
503416 VS.DataDiscardRatio.Max
86
503416 VS.DataDiscardRatio.Min
87
503416 VS.PdschCodeUsed.Mean
88
503416 VS.PdschCodeUsed.Max
89
503416 VS.PdschCodeAvail.Mean
90
Issue 04 (2013-05-10)
10-29
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
codes in a cell
Feature ID
Feature
Name
Package
503416 VS.PdschCodeAvail.Max
91
Maximum
number of
available
HS-PDSCH
codes in a cell
503416 VS.PdschCodeUsed.Min
92
503416 VS.HSDPA.InactiveDataTtiRatio.Mean
93
503416 VS.HSDPA.2ScchCodeRatio
94
503416 VS.HSDPA.3ScchCodeRatio
95
503416 VS.HSDPA.4ScchCodeRatio
96
503416 VS.HSDPAPwrRatio.Mean.FreeUser
97
Average usage
of free users
Hsdpa Power
503416 VS.HSDPAPwrRatio.Max.FreeUser
98
503416 VS.DataOutput.Mean.FreeUser
99
Issue 04 (2013-05-10)
10-30
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
MAC-hs/MAC-eh
s layer
Feature
Name
Package
503417 VS.DataOutput.Max.FreeUser
00
503417 VS.DataOutput.Min.FreeUser
01
Number of
BSC69 WRFD-0106 HSDPA
Successful
00
10
Introduction
HSDPA MAC-d
Package
Flow
Establishments
for Cell
Number of
BSC69 WRFD-0106
Intra-RNC
00
1006
HSDPA Serving
Cell Change
Attempts for Cell
HSDPA
Mobility
Manageme
nt
671906 VS.HSDPA.SHO.ServCellChg.SuccOut
99
Number of
BSC69 WRFD-0106
Intra-RNC
00
1006
HSDPA Serving
Cell Change
Success in RNC
HSDPA
Mobility
Manageme
nt
Issue 04 (2013-05-10)
10-31
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
for Cell
671907 VS.HSDPA.HHO.H2H.AttOutIntraFreq
00
Number of
BSC69 WRFD-0106
Intra-Frequency 00
1006
HSDPA Hard
Handover
Attempts Without
Channel Change
for Cell
HSDPA
Mobility
Manageme
nt
671907 VS.HSDPA.HHO.H2H.SuccOutIntraFreq
01
Number of
BSC69 WRFD-0106
Successful
00
1006
Intra-Frequency
HSDPA Hard
Handovers
Without Channel
Change for Cell
HSDPA
Mobility
Manageme
nt
671907 VS.HSDPA.HHO.H2H.AttOutInterFreq
02
Number of
BSC69 WRFD-0106
Inter-Frequency 00
1006
HSDPA Hard
Handover
Attempts Without
Channel Change
for Cell
HSDPA
Mobility
Manageme
nt
671907 VS.HSDPA.HHO.H2H.SuccOutInterFreq
03
Number of
BSC69 WRFD-0106
Successful
00
1006
Inter-Frequency
HSDPA Hard
Handovers
Without Channel
Change for Cell
HSDPA
Mobility
Manageme
nt
671907 VS.HSDPA.HHO.NoChR.Att.NCell
08
Number of
BSC69 WRFD-0106
HSDSCH-to-HS 00
1006
DSCH hard
Handover
Requests
Without Channel
Change Between
Neighboring
Cells
HSDPA
Mobility
Manageme
nt
671907 VS.HSDPA.HHO.NoChR.Succ.NCell
09
Number of
BSC69 WRFD-0106
Successful
00
1006
HSDSCH-to-HS
DSCH hard
Handovers
Without Channel
HSDPA
Mobility
Manageme
nt
Issue 04 (2013-05-10)
10-32
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
Change Between
Neighboring
Cells
671907 VS.HSDPA.ServCellChg.Att.NCell
10
Number of
BSC69 WRFD-0106
HSDPA Serving 00
1006
Cell Change
Attempts
Between
Neighboring
Cells
HSDPA
Mobility
Manageme
nt
671907 VS.HSDPA.ServCellChg.Succ.NCell
11
Number of
BSC69 WRFD-0106
Successful
00
1006
HSDPA Serving
Cell Changes
Between
Neighboring
Cells
HSDPA
Mobility
Manageme
nt
671911 VS.IRATHO.HSDPA.AttOutPSUTRAN
55
HSDPA
Mobility
Manageme
nt
671911 VS.IRATHO.HSDPA.SuccOutPSUTRAN
56
Number of
BSC69 WRFD-0106
Successful PS 00
1006
Outgoing
Inter-RAT
Handovers for
HSDPA Services
for Cell
HSDPA
Mobility
Manageme
nt
671911 VS.HSDPA.HHO.H2D.AttOutIntraFreq
57
Number of
BSC69 WRFD-0106
Intra-Frequency 00
1006
H2D Hard
Handover
Attempts for Cell
HSDPA
Mobility
Manageme
nt
671911 VS.HSDPA.HHO.H2D.SuccOutIntraFreq
58
Number of
BSC69 WRFD-0106
Successful
00
1006
Intra-Frequency
H2D Hard
Handovers for
Cell
HSDPA
Mobility
Manageme
nt
Issue 04 (2013-05-10)
10-33
WCDMA RAN
HSDPA
10 Counters
Counter
Description
671911 VS.HSDPA.HHO.H2D.AttOutInterFreq
59
Number of
BSC69 WRFD-0106
Inter-Frequency 00
1006
H2D Hard
Handover
Attempts for Cell
HSDPA
Mobility
Manageme
nt
671911 VS.HSDPA.HHO.H2D.SuccOutInterFreq
60
Number of
BSC69 WRFD-0106
Successful
00
1006
Inter-Frequency
H2D Hard
Handovers for
Cell
HSDPA
Mobility
Manageme
nt
HSDPA
Introduction
Package
HSDPA
Introduction
Package
HSDPA
Introduction
Package
671934 VS.LCC.HSDPA.CodeAdj.Succ
10
HSDPA
Introduction
Package
671935 VS.HSDPA.UE.Max.CAT1.6
78
Issue 04 (2013-05-10)
NE
Feature ID
Feature
Name
Overload
Control
Overload
Control
Overload
Control
Code
Resource
Manageme
nt
Maximum
BSC69 WRFD-0106 HSDPA UE
Number of
00
1002
Category 1
HSDPA UEs with
to 28
Category 1-6 in a
10-34
WCDMA RAN
HSDPA
10 Counters
Counter
Description
NE
Feature ID
Feature
Name
Cell
671935 VS.HSDPA.UE.Max.CAT7.10
81
Maximum
BSC69 WRFD-0106 HSDPA UE
Number of
00
1002
Category 1
HSDPA UEs with
to 28
Category 7-10 in
a Cell
671935 VS.HSDPA.UE.Max.CAT11.12
84
Maximum
BSC69 WRFD-0106 HSDPA UE
Number of
00
1002
Category 1
HSDPA UEs with
to 28
Category 11-12
in a Cell
671935 VS.HSDPA.UE.Max.CAT13.14
87
Maximum
BSC69 WRFD-0106 HSDPA UE
Number of
00
1002
Category 1
HSDPA UEs with
to 28
Category 13-14
in a Cell
671935 VS.HSDPA.UE.Max.CAT15.16
90
Maximum
BSC69 WRFD-0106 HSDPA UE
Number of
00
1002
Category 1
HSDPA UEs with
to 28
Category 15-16
in a Cell
671935 VS.HSDPA.UE.Max.CAT17.20
93
Maximum
BSC69 WRFD-0106 HSDPA UE
Number of
00
1002
Category 1
HSDPA UEs with
to 28
Category 17-20
in a Cell
671935 VS.HSDPA.UE.Max.CAT21.24
96
Maximum
BSC69 WRFD-0106 HSDPA UE
Number of
00
1002
Category 1
HSDPA UEs with
to 28
Category 21-24
in a Cell
671954 VS.HSDPA.SHO.ServCellChg.AttOutIur
81
Number of
BSC69 WRFD-0106
Inter-RNC
00
1006
HSDPA Serving
Cell Change
Attempts for Cell
HSDPA
Mobility
Manageme
nt
671954 VS.HSDPA.SHO.ServCellChg.SuccOutIur
82
Number of
BSC69 WRFD-0106
Inter-RNC
00
1006
HSDPA Serving
Cell Change
Success for Cell
HSDPA
Mobility
Manageme
nt
Issue 04 (2013-05-10)
10-35
WCDMA RAN
HSDPA
10 Counters
Counter
Description
671954 VS.HSDPA.HHO.H2H.AttOutIur
83
Number of
BSC69 WRFD-0106
Inter-RNC
00
1006
HSDPA Hard
Handover
Attempts Without
Channel Change
for Cell
HSDPA
Mobility
Manageme
nt
671954 VS.HSDPA.HHO.H2H.SuccOutIur
84
Number of
BSC69 WRFD-0106
Successful
00
1006
Inter-RNC
HSDPA Hard
Handovers
Without Channel
Change for Cell
HSDPA
Mobility
Manageme
nt
671959 VS.LCC.HSDPA.CodeAdj.Att
92
HSDPA
Introduction
Package
NE
Feature ID
Feature
Name
Overload
Control
672028 VS.HSDPA.MeanChThroughput
94
672042 VS.HSDPA.UE.Mean.CAT1.6
59
672042 VS.HSDPA.UE.Mean.CAT7.10
60
672042 VS.HSDPA.UE.Mean.CAT11.12
61
672042 VS.HSDPA.UE.Mean.CAT13.14
62
Issue 04 (2013-05-10)
10-36
WCDMA RAN
HSDPA
10 Counters
Counter
Description
672042 VS.HSDPA.UE.Mean.CAT15.16
63
672042 VS.HSDPA.UE.Mean.CAT17.20
64
672042 VS.HSDPA.UE.Mean.CAT21.24
65
733938 VS.HSDPA.MACD.AttSetup
28
Number of
BSC69 WRFD-0106 HSDPA
HSDPA MAC-d 00
10
Introduction
Flow
Package
Establishment
Requests for Cell
734037 VS.HSDPA.HHO.H2D.AttOutIur
64
number of
BSC69 WRFD-0106
Inter-RNC H2D 00
1006
Hard Handover
Attempts for Cell
HSDPA
Mobility
Manageme
nt
734037 VS.HSDPA.HHO.H2D.SuccOutIur
65
Number of
BSC69 WRFD-0106
Successful
00
1006
Inter-RNC H2D
Hard Handovers
for Cell
HSDPA
Mobility
Manageme
nt
734104 VS.SRNCIubBytesHSDPA.Tx
99
Number of DL
BSC69 WRFD-0106 HSDPA
Bytes over Iub 00
10
Introduction
HSDSCH for Cell
Package
734221 VS.HSDPA.RAB.AbnormRel.H2P
67
Issue 04 (2013-05-10)
NE
Feature ID
Feature
Name
UE State in
Connected
Mode
(CELL-DCH
,
CELL-PCH,
URA-PCH,
CELL-FAC
H)
HSDPA
Introduction
Package
10-37
WCDMA RAN
HSDPA
10 Counters
Counter
Description
734234 VS.HSDPA.Traffic.HighLoad
62
734411 VS.HSDPA.MeanChThrouput.HighLoad
41
Issue 04 (2013-05-10)
Mean
Throughput on
HSDPA MAC-d
Flow for Cell
(Excluding the
Data of
Low-Traffic
Users)
NE
Feature ID
Feature
Name
HSDPA
Introduction
Package
Interactive
and
Background
Traffic
Class on
HSDPA
10-38
WCDMA RAN
HSDPA
11 Glossary
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
Issue 04 (2013-05-10)
11-1
WCDMA RAN
HSDPA
12 Reference Documents
12 Reference Documents
[1] 3GPP TS 25.214, "Physical layer procedures (FDD)"
[2] 3GPP TS 25.306, "UE Radio Access capabilities"
[3] 3GPP TS 25.308, "UTRA High Speed Downlink Packet Access (HSDPA); Overall description"
[4] 3GPP TS 25.433, "UTRAN Iub interface NBAP signaling"
[5] 3GPP TS 25.435, "UTRAN Iub interface user plane protocols for CCH data flows"
[6] Transmission Resource Management Feature Parameter Description
[7] Load Control Feature Parameter Description
[8] Call Admission Control Feature Parameter Description
[9] Directed Retry Decision Feature Parameter Description
[10] Differentiated HSPA Service Feature Parameter Description
[11] Radio Bearers Feature Parameter Description
[12] State Transition Feature Parameter Description
[13] Power Control Feature Parameter Description
[14] Handover Feature Parameter Description
[15] HSPA Evolution Feature Parameter Description
[16] QoS Management Feature Parameter Description
[17] License Management Feature Parameter Description
Issue 04 (2013-05-10)
12-1