Professional Documents
Culture Documents
Objective
Increased UL average and peak data rates improve the end user experience. CAPEX
and OPEX savings result from increased cell UL capacity and increased Iub and BTS HW
efficiency. New data service availability increases revenue
Hardware Requirement
This feature does not require any new or additional Hardware
Software Sales Information
Overview : Objective:
72 simultaneous HSPA users (HSDPA and HSUPA)
High number of users with
per cell:
efficient data throughput per user
Support for high number of voice users over HSPA
Dynamic allocation of DL control
Support of high number of always on users on
channels maximizes capacity for
HSPA
HSDPA
Increased number of HSDPA and HSUPA DL
control channels
HSPA users
80
64 72 72
48 64 60
32 48
16 24
DL/cell UL/BTS DL/cell UL/BTS DL/cell UL/cell
RAS06 RU10 RU20
23 ©2013 Nokia Solutions and Networks. All rights reserved.
HSPA 72 User per Cell Feature Description (ii)
Summary:
This feature increases the number of simultaneous HSPA (HSDPA and HSUPA) users
to 72 per cell. Due to this increase, the number of DL HSDPA and HSUPA control
channels is increased. Additionally, dynamic allocation of the DL code space used by
these channels is enhanced
Benefits for the operator:
End user benefits
With this feature more users can be kept on HSPA, providing an instant access to
data services after momentary inactivity periods and thus improving the end user
experience
Operator benefits
The introduction of this feature creates pre-conditions for support for high number
of voice users
Requirement
Software Requirement
Functional description:
This feature allows 72 simultaneous HSPA (HSDPA & HSUPA) users per cell, both with
dedicated and shared scheduler. In order to be able to schedule and control increased
number of HSPA users in a cell, the number of HS-SCCH channels is increased to four.
On the other hand, as the DL code space is a scarce resource, a dynamic DL control
channel allocation mechanism is introduced to maximize the available codes for HS-
PDSCHs. E-HICH/E-RGCH codes are allocated dynamically, based on number of users.
In order to avoid fragmentation of the code space, the E-HICH/E-RGCH signatures are
actively reconfigured
Overview :
Benefits:
HSUPA peak rate is increased up to 5.8Mbps/user
• Higher HSUPA peak rates up to 5.8
2ms TTI on the air interface and Iub
Mbps
RTT is decreased 12-15 ms
• Decreased Round Trip Time
Functional description:
HSUPA 2ms TTI is used for UE categories 2, 4, 6 and 7 Shorter TTI improves average
latency in radio interface by 12ms for the first transmission. Faster retransmissions
also reduce variance of the Round Trip Time (RTT). Immediate data processing in Iub
and the RNC user plane also shortens RTT. Mapping the SRBs to HSUPA enables
spreading code allocation of 2xSF2 + 2xSF4 in uplink which is needed if 5.8 Mbps
bitrate is used
Functional description:
HSUPA UE categories 4, 6 and 7 support higher peak bit rate than 2 Mbps. With this
feature, category 4, 6 and 7 UEs may transmit data with their maximum bit rate,
which is achieved with an E-DCH configuration of 2 ms transmission time interval
(TTI). Four parallel codes are required for category 6 and 7. When four codes are
transmitted in parallel, two codes are transmitted with spreading factor two (2xSF2)
and two with spreading factor four (2xSF4). Also intermediate bit rates are supported
with 2 ms TTI. The maximum theoretical throughput of category 6 and 7 terminal is
5.76 Mbps. Practical throughput achievable with this feature is limited by radio
System Impact:
Interdependency between Feature
This feature requires RAN1470: HSUPA 2 ms TTI
Impact of Interfaces :
UU: Adaptation of RRC signaling to support 2 ms TTI and SRB on E-DCH
Iub: New set of Call Admission Control parameters related to SRB on E-DCH
Impact of Parameter :
Note that the RAN981: HSUPA 5.8 Mbps feature can be activated only if the RAN1470:
HSUPA 2 ms TTI feature is enabled in a cell.
Note that with the current default value of the WCEL PrxMaxTargetBTS parameter,
the maximum UL bit rate may not be reached. Therefore, it is advised to increase the
value of the PrxMaxTargetBTS parameter