RAS06 Delta Module2 Features & Main Parameters

RAS06 Delta Optimization
Module 2 Feature & Parameter update
Soc Classification level 1 Nokia Siemens Networks
Presentation / Author / Date
CONTENTS
Module 1 RAS06 Optimization Delta training -Introduction Module 2 Feature & Parameter update Module 3 Configuration Management Module 4 Drive test analysis Module 5 Performance Monitoring update Module 6 Neighbour Optimization Module 7 Capacity Management Update Module 8 RAN troubleshooting
Module 2 Feature and Parameter update

Objectives After this module the participant shall be able to: Understand RAS06 new functionality compared to RAS5.1 Describe main RAS06 Radio parameters which are useful in optimization
Module Contents
RAS06 main features HSDPA resource handling
HSDPA Dynamic Resource Allocation HSDPA code multiplexing HSDPA associated uplink DPCH scheduling
HSUPA resource handling

Mobility SCC vs. HSUPA SHO
Enhanced HSDPA mobility handling
Summary of RAS06 HSPA Features

HSDPA RRM/Telecom Features
RAS06 features can be split to HSDPA Telecom HSUPA Telecom HSPA Layering
16 kbit/s Return Channel DCH Data Rate Support for HSDPA HSDPA 15 Codes (requires RAN312, RAN1033 or RAN1034) HSDPA Code Multiplexing (requires RAN312 & RAN852)) HSDPA 48 Users per Cell Shared HSDPA Scheduler for Baseband Efficiency HSDPA Dynamic Resource Allocation + Direct switch + Dynamic HSDPA code allocation + Dynamic DCH scheduling + Dynamic HSDPA Power Allocation HSDPA 10 Mbps per User HSDPA 14.4 Mbps per Cell HSUPA RRM/Telecom Features
Feature Number RAN1013 RAN852 RAN853 RAN1033 RAN1034 RAN312
RAS06 Optional Optional Optional Optional Optional Basic Optional Optional
RAN1249 RAN1305 Feature Number
Optional Basic RAS06
Basic HSUPA HSUPA Basic RRM HSUPA BTS Packet Scheduler HSUPA 2.0 Mbps HSUPA Handovers HSUPA Congestion Control HSUPA with Simultaneous AMR Voice Call
HSPA RRM/Telecom Features HSPA Layering for UEs in Common Channels
RAN826 Basic RAN973 Basic RAN968 Basic RAN979 Optional RAN970 Basic RAN992 Basic RAN974 Optional
Feature Number RAN1011 RAS06 Optional
HSDPA Features Resource allocation

HSDPA Basic functionality
HSDPA resource allocation
Static code and power in RNC
Optional enhanced functionality

HSDPA Dynamic Resource Allocation
Dynamic NRT DCH Scheduling Dynamic allocation of HS-PDSCH codes
HSDPA uplink associated DPCH scheduling HSDPA Channel Switching

Possible via cell FACH or DCH 0/0
+ 16 kbit/s Return Channel DCH Data Rate Support for HSDPA Direct switching between DCH and HSDSCH + HSDPA 15 Codes & code multiplexing
Basic HSDPA with QPSK and 5 Codes HSDPA 16-QAM Support
RAS06 features
Soc Classification level 6 Nokia Siemens Networks Presentation / Author / Date
HSDPA Features Mobility, multi-RABs, Number of HSDPA users

HSDPA Basic functionality HSDPA Serving Cell Change and HSDPA Soft/Softer Handover for Associated DPCH HSDPA Cell Reselection Optional enhanced functionality
HSPA SCC over Iur, Inter Frequency HSPA Mobility
HSDPA with Additional RAB Initiation, HSDPA suspension
+ HSPA with Simultaneous AMR Voice Call
HSDPA 16 Users per Cell
+ HSPA 48 Users per Cell
RAS06 features
HSDPA Dynamic Resource Allocation (DRA)

This feature allocates Dynamically HSPDA power and HS-PDSCH Codes Dynamic power allocation
HSDPA power limitation is not sent from RNC to BTS, it is always dynamic in BTS
RNC allocates NRT DCH power like in RAS5.1 BTS allocates all available DL power for HSDPA There is Dynamic NRT DCH scheduling between R99 and HSDPA power There is Prioritisation between NRT DCH and HSDPA traffic/power Dynamic allocation of HS-PDSCH codes with HSDPA 15 codes feature
Dynamic Code Allocation
RNC applies HSDPA dynamic resource allocation if Parameter HSDPADynamicResourceAllocation is set to Enabled
HSDPA 15 Codes (14.4 Mbps per cell and 10 Mbps per user)
In RAS06 it is possible to have HS-PDSCH codes up to 10 or 15 with HSDPA 15 codes and Dynamic Resource allocation features Average cell HSDPA throughput is increased
Features Modulation UE category Number of HS-PDSCH codes Air interface bit rate (Mbps) Max. transport block size (bits) Max. transport channel (MAC-d flow) bit rate (Mbps) RLC PDU (bits) RLC blocks/TTI RLC bit rate (Mbps) RLC payload (Mbps) QPSK QPSK Cat 11-12 5 2,4 3630 1,815 336 10 1,68 1,6 16-QAM 16-QAM Cat 6 5 4,8 7298 3,649 336 21 3,528 3,36 + 15 code 16-QAM Cat 7-8 10 9,6 14155 7,0775 336 42 7,056 6,72 + 10 Mbps 16-QAM Cat 9-10 15 14,4 20251 10,1255 336 60 10,08 9,6 14.4 Mbps user 1 16-QAM Cat 9-10 8 7,68 14936 7,468 336 44 7,392 7,04 14.4 Mbps user 2 16-QAM Cat 9-10 7 6,72 13177 6,5885 336 39 6,552 6,24 13,944 13,28 14,0565 14,4 14.4Mbps Total
HSDPA Code Multiplexing

Allows sending data for more than one user in same TTI Needed when network supports more codes than UEs
HSDPA code multiplexing will enable the cell throughput increase achievable with 10/15 codes also with 5 code UEs in the network.
A peak cell level throughput of 10 Mbps can be achieved with code multiplexing of three 5 code UEs.
Simultaneous HSDPA users needed in the network to get the capacity gain
Depending on the number of codes up to 3 HS-SCCHs used Example below with two parallel users
HS-SCCHs
= User 1 = User 2
Control data
HS-DSCH
Demodulation information
User data
2 ms
RAS06:Shared HSDPA Scheduler/48 users per cell- flexi rel 1

10 users 22 users 16 users
Shared HSDPA Scheduler for Baseband Efficiency

Up to 10.8 Mbps per BTS Max 15 codes per cell, 45 codes for BTS Max 48 Users per BTS 80 CE from FSMB allocated to HSDPA scheduler 1 scheduler per BTS
Example 3: Shared HSDPA Scheduler for BB Efficiency 1*80 CE
48 Users per Cell
Up to 14.4 Mbps per cell (with code multiplexing)

Max 15 codes per cell 80 CE from FSMB allocated per HSDPA scheduler (=per cell) = 240 CEs (1+1+1) Max 5 schedulers per BTS (5*80=400CE)
Example 4: 48 Users per cell 3*80CE

RAS06:Shared HSDPA Scheduler/48 users per cell- ultra

3.

Shared HSDPA Scheduler for Baseband Efficiency

Up to 10.8 Mbps per BTS Max 15 codes per cell, 45 codes for BTS Max 48 Users per BTS 64 CE from WSPC allocated per HSDPA scheduler
Example 3: Shared HSDPA Scheduler for BB Efficiency 1*64 CE
4.
48 Users per Cell

Up to 14.4 Mbps per cell (with code multiplexing)
Max 15 codes per cell 64 CE from WSPC allocated per HSDPA scheduler (=per cell)
Example 4: 48 Users per cell 3*64CE =192

Several 16 Users per BTS Schedulers in BTS by Tcell grouping from RNC
B
11 users
Tcell = 4
5 users
Tcell = 3
16 users
Tcell = 0
16 Users per BTS Scheduler -feature requires 32 CE of processing capacity to be enabled for one to three cells in the BTS. Another 32 CEs can be added so that cell A (blue) is handled by first 32 CE and cells B (yellow) and C (yellow) by the second 32 CEs. Cells are grouped to each scheduler with Tcell parameter from RNC. Max 4 schedulers per BTS Rules for grouping (max 4 groups): Group 1: Tcell values 0, 1 and 2 Group 2: Tcell values 3, 4 and 5 Group 3: Tcell values 6, 7 and 8 Group 4: Tcell value 9
Example 1: 1+1+1: 2 x32 CE
f1
Tcell = 3
Tcell = 0
16 users
Tcell = 2
Tcell = 1
4 schedulers (max 5 codes and 16 users): F1: 3 cells sharing one scheduler F2: 1 scheduler per cell
f2
16 users 16 usersTcell = 6 16 users

Tcell = 9
2+2+2: 4 x32 CE
Maximum number of HSDPA schedulers simultaneously active
* Usage of Tcell parameter required Note that only one type of scheduler can be used in BTS at a time
HSUPA
Basic HSUPA throughput can be up to 1.44 Mbps/user but it can be maximum 2.0 Mbps/user with separate feature. This depends on the UE category also. 2*SF2 and 2*SF4 Supported max 24 HSUPA users per BTS max 20 HSUPA users per cell Support for AMR call with PS connection over HSUPA Soft/softer Handovers are supported with new HSPA specific FMCS parameter set
Max L1 data rate/user UE category # of codes 10 ms 2 ms
1 2 3 4 5 6
1 x SF4 2 x SF4 2 x SF4 2 x SF2 2 x SF2

2 x SF2 + 2 x SF4
0.71 Mbps 1.45 Mbps 1.45 Mbps 2.0 Mbps 2.0 Mbps 2.0 Mbps
1.45 Mbps 2.8 Mbps 5.74 Mbps
E-DCH serving cell is always same as HSDSCH serving cell
HSUPA HSDPA AMR

HSUPA Packet Scheduler

Node B uses both throughput and power based scheduling in air interface
Minimum throughput can be allocated regardless of the interference
Node B allocates baseband resources based on both the number of HSUPA connections and the load generated by the DCH traffic
Prx RNC PS DCH scheduling domain
Throughput-based
Power-based
PrxMaxTargetBTS
PrxLoadMarginEDCH
Load
HSUPA Round Trip Time 52 ms

NSN Nokia End-to-end Measurement Low round trip time (=latency) improves end user and protocol performance Nokia Siemens HSUPA shows excellent round trip time Measured end to end IP level round trip time on average 52 ms and the minimum value 40 ms
Nokia Siemens networks
Nokia HSUPA terminal prototype
Node-B
RNC
Packet core
Server
Approximate round trip times: Minimum = 40ms, Maximum = 66ms, Average = 52ms
Module Contents
HSDPA resource handling
HSDPA Dynamic Resource Allocation Dynamic power allocation Dynamic NRT DCH scheduling Prioritisation between HSDPA and NRT DCH power resources Dynamic Code Allocation HSDPA code multiplexing HSDPA associated uplink DPCH scheduling
HSUPA resource handling Enhanced HSDPA mobility handling
HSDPA power allocation methods

HSDPA (Static) Resource Allocation HSDPADynamicResourceAllocation Disabled RNC sends the PtxMaxHSDPA to BTS BTS allocates the available DL power dynamically to HSDPA until PtxMaxHSDPA RNC schedules NRT DCH according to HSDPApriority
HSDPA dynamic Resource Allocation
Enabled BTS allocates the available DL power dynamically to HSDPA until PtxCellMax/ MaxDLPowerCapability DL power RNC schedules NRT DCH using dynamic NRT scheduling
Min(PtxMaxHSDPA,min(PtxCellMax,MaxDLPowerCapability )-PtxTargetHSDPA)
HSPA Power
BTS periodically reports the total transmission power value PtxTotal and non-HSDPA power Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission if BTS supports only HSDPA or non-HSPA power (Transmitted carrier power of all codes not used for HS-PDSCH HS-SCCH E-AGCH E-RGCH or E-HICH transmission) if BTS supports HSUPA to RNC in RRI messages These two are referenced as HSxPA power The reported values are in range 0100% representing the power value relative to the cell maximum transmission power, defined by MIN[PtxCellMax, MaxDLPowerCapability] From the difference of reported PtxTotal and HSxPA power, RNC can calculate the used HSPA-power value and update that to statistics counters The counters are updated only when there is at least one HSDPA allocation in the cell RNC updates the HSxPA power value counters when nbap_radio_resource_ind_s message including PtxTotal and HSxPA power information is received from BTS and there is at least one HSDPA allocation in the cell The unit for all counter updates is watt
Dynamic HSDPA Power allocation

When the Dynamic Resource Allocation feature is enabled in RAS06, the HSDPA power allocation procedure changes considerably in the RNC side RNC does not signal HSDPA power to BTS and BTS will allocate all available DL power to HSDPA until PtxMax PtxMax = min(PtxCellMax, MaxDLPowerCapability) RNC schedules the NRT DCH traffic until PtxTargetPS threshold. PtxTarget remains as a target for NRT load even if there is one or more HS-DSCH MAC-d flows setup in the cell. RNC adapts PtxTragetPS threshold according to current NRT DCH and HSDPA traffic amount and respective priority settings HSDPA active
PtxMax PtxHSDPA PtxTotal PtxHighHSDPAPwr PtxTarget +PtxOffset PtxTargetPSMax PtxTargetPS PtxTargetPSTarget PtxTargetPSMin
PtxNonHSPA
PtxNRT PtxNC
Module Contents
Dynamic NRT DCH scheduling

RNC affects the HSDPA power allocation indirectly by scheduling NRT DCH bit rates When there is at least one HS-DSCH MAC-d flow allocated in the cell, PtxTargetPS is used for packet scheduling and handover control purposes (this was PtxTargetHSDPA for R99 in RAS5.1) PtxTargetPS is adjusted between PtxTargetPSMin and PtxTargetPSMax
PtxTargetPSMin PtxTargetPS PtxTargetPSMax

PtxTargetPSAdjustPeriod defines the adjustment period for the PtxTargetPS in terms of Radio Resource Indication (RRI) reporting periods If PtxTargetPSMax and PtxTargetPSMin are set to the same value, RNC does not adjust PtxTargetPS Dynamic NRT DCH scheduling disabled
Dynamic NRT DCH scheduling

With no active HSDPA users: 1) NRT DCH scheduling to the PtxTarget+PtxOffset &RT DCH admission to PtxTarget No HSDPA users PtxTotal 3 1 2 PtxNonHSPA PtxNC
With active HSDPA users: 2) NRT DCH scheduling to PtxTargetPS 3) RT DCH admission to PtxTarget No HSDPA users PtxMax
HSDPA active
PtxHSDPA
PtxTarget +PtxOffset PtxTargetPS PtxNRT
Dynamic NRT DCH scheduling Adjustment

Initial value of the PtxTargetPS is the lower from the following ones: PtxTarget or PtxTargetPSMax
Initial value is taken into use when the first HS-DSCH MAC-d flow is setup
Usage ends when the last HS-DSCH MAC-d flow is deleted

PtxTarget remains as a target for non-controllable load even if there are one or more HS-DSCH MAC-d flows setup in the cell
PtxTargetPS is adjusted based on received PtxTotal (Transmitted Carrier Power) and PtxNonHSPA
PtxNonHSPA = Transmitted carrier power of all codes not used for HS-PDSCH, HSSCCH, E-AGCH, E-RGCH or E-HICH transmission
PtxTargetPS is adjusted only when there are NRT DCH users - in addition to the HS-DSCH MAC-d flow(s) - in the cell. Adjustment of the PtxTargetPS is done in fixed steps, defined by the PtxTargetPSStepUp and PtxTargetPSStepDown management parameters
Dynamic NRT DCH scheduling Power congestion

Adjustment of the PtxTargetPS is executed when power congestion for DL transport channel type (HS-DSCH or NRT DCH) is detected by the RNC The definition of the power congestion for DL transport channel type in this context is defined as follows
Power congestion for DL HS-DSCH transport channel type is detected when the following condition is effective:
PtxTotal PtxHighHSDPAPwr
PtxHighHSDPAPwr is an operator adjustable management parameter
Power congestion for DL DCH transport channel type is detected when the following condition is effective:
PtxNonHSPA (PtxTargetPS Offset) Fixed value 1 dB used for Offset
Dynamic NRT DCH scheduling PtxTargetPS decrease

PtxTargetPS is decreased if
PtxTotal > PtxHighHSDPAPwr
= HSDPA power congestion
MAC-d flow(s) setup in the cell NRT DCH user(s) in the cell
PtxTotal received
& PtxTargetPS > PtxTargetPSTarget

Above target value
PtxTotal >= PtxHighHSDPAPwr No
Amount of decrease is determined by the management parameter PtxTargetPSStepDown, but limited to

PtxTargetPS PtxTargetPSTarget
Yes
PtxTargetPS > PtxTargetPSTarget
No
Yes
Decrease PtxTargetPS
No decrease Check increase
PtxTargetPSTarget = target (ideal) value of the NRT DCH scheduling target

Dynamic NRT DCH scheduling PtxTargetPS increase

PtxTargetPS is increased if
PtxNonHSPA > PtxTargetPS - 1 dB
= Power congestion on DCH
PtxNonHSPA received MAC-d flow(s) setup in the cell NRT DCH user(s) in the cell
& PtxTargetPS < PtxTargetPSTarget

Below target value
PtxNonHSPA >= (PtxTargetPS - 1 dB) No Yes
Amount of increase is determined by the management parameter PtxTargetPSStepUp
PtxTargetPS < PtxTargetPSTarget
No
Yes No increase Check decrease
Increase PtxTargetPS
PtxTargetPSTarget = target (ideal) value of the NRT DCH scheduling target
Dynamic NRT DCH scheduling Summary

1) Power congestion for HSDPA: PtxTotal PtxHighHSDPAPwr Decrease PtxTargetPS down to PtxTargetPSTarget 1 PtxTotal 2) Power congestion for NRT DCH: PtxNonHSPA (PtxTargetPS 1 dB) Increase PtxTargetPS upto PtxTargetPSTarget
HSDPA active
PtxMax
PtxHSDPA
PtxHighHSDPAPwr
PtxTarget +PtxOffset
PtxTargetPSMax
PtxTargetPS 2 PtxNonHSPA
PtxTargetPSTarget
PtxTargetPSMin
PtxNRT PtxNC
DRA_Test
1. 2. 3. 4. 5.
Start HSDPA Download N95 Start 4xDCH Stop HSDPA Start HSDPA download N95 Stop 4x DCH
PtxMaxHSDPA = 43 dBm=20W PtxTargetPSMax = 40 dBm=10W PtxTargetPSMin = 36 dBm= PtxTarget = 42 dBm
1st HSDPA call (N95)

25,0
When there is no active HSDPA call under the cell, the NRT Ptx DCHs can be scheduled until Ptxtarget instead of PtxTargetPSMax
2nd HSDPA call (N95)
20,0
15,0
10,0
5,0
0,0 0 -5,0
s
22
44
65
87
109
131
153
175
196
218
240
262
284
305
327
349
371
Increased NRT DCH traffic decrease HSDPA power
HSDPA
NRT DCH
PtxTotal
Online monitoring example, PtxTotal is total power

When there is no R99 traffic in the cell, the HSDPA will get all free power
HS-PDSCH Transmit Power with DRA Limited by PtxMaxHSDPA, TN 107-2008

HSDPA power is limited by the PtxMaxHSDPA parameter even with DRA
PtxMaxHSDPA should be increased from RAS5.1 value close or equal to Cell Maximum Tx Power for efficient HSDPA resources with DRA Without DRA Max HSDPA power =min(PtxMaxHSDPA, PtxMax - PtxTargetHSDPA)
Ptx
Cell maximum TX power
PtxCellMax = 46 dBm (40W WPA)
HSDPA
Non-HSDPA power
Common chs
Time
Maximum HSDPA power (PtxMaxHSDPA)

Dynamic Power Allocation and NRT Scheduling Parameters

HSDPADynamicResourceAllocation Range:0 (Disabled), 1 (Enabled), Default:0, Object:RNC HSDPApriority Range:1 (HSDPA priority 1), 2 (HSDPA priority 2), Default:1, Object:RNC PtxCellMax Range and step: 0..50 dBm, step 0.1 dBm, Default: 43 dBm, Object:WCEL MaxDLPowerCapability Range and step: 0..50 dBm, step 0.1 dBm Default value: -, Default value notes: Value set by the system, Object: WCEL PtxTargetPSMin Range:-10..50 dBm, step 0.1 dBm, Default:36 dBm, Object:WCEL PtxTargetPSMax Range:-10..50 dBm, step 0.1 dBm, Default:40 dBm, Object:WCEL PtxTargetPSAdjustPeriod Range:1..255, step 1, Default:10O, bject:WCEL PtxTargetHSDPA Range:-10 50 dBm, step 0.1 dBm, Default:38.5 dBm, Object:WCEL PtxOffsetHSDPA Range:0 6 dB, step 0.1 dB, Default:0.8 dB, Object:WCEL PtxTargetPSStepUp Range:-0..5 dB, step 0.1 dB, Default:1 dB, Object:WCEL PtxTargetPSStepDown Range:-0..5 dB, step 0.1 dB, Default:1 dB PtxHighHSDPAPwr Range:-10..50 dBm, step 0.1 dBm, Default:41 dBm, Object:WCEL
Dynamic Power Allocation and NRT Scheduling Parameters

WCEL parameters in NEMU
RNC parameters in NEMU
Example-Throughput per UE Type and PtxMaxHSDPA: Mobile Route

Nokia N95
Throughput CDF v UE Type & PtxMaxHSDPA
1 0.9 0.8 0.7 E870 39dBm E870 43dBm N95 39dBm N95 43dBm
Category 6 terminal 16QAM modulation Support a max of 5 codes Max theoretical throughput ~3.6 Mbps
CDF %
0.6 0.5 0.4 0.3 0.2 0.1 0
Huawei E870 Mobile Connect

1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 0 500
HSDPA Category 8 terminal HSUPA Category 5 terminal 16QAM modulation Support a max of 10 codes Max theoretical throughput ~7.2Mbps
Throughput (kb/s)
Gain for N95 averages ~ 150kb/s with higher HSDPA power

For E870 gain is higher ~ 500kb/s
Example-Throughput v CQI
Huawei E870 Throughput (L1) v CQI PtxMaxHSDPA = 43dBm 7000000
4000000 3500000 N95 Throughput (L1) v CQI PtxMaxHSDPA=43dm
MAC-hs Throughput (b/s)
MAC-hs Throughput (b/s)
6000000 5000000 4000000 3000000 2000000 1000000 0 5 10 15 Ave Reported CQI 20 25
3000000 2500000 2000000 1500000 1000000 500000 0 0 5 10 15 Ave Reported CQI 20 25 30
Actual MAC-hs throughput characteristics are quite different, and idle TTIs are impacting.
Samples sitting below the curves are typically in the slow-start or serving-cell change periods.
Module Contents
Prioritisation between HSDPA and DCH resources

Dynamic NRT DCH scheduling algorithm utilises dynamic priorisation between HSDPA and NRT DCH traffic types RNC follows the priorisation of the traffic types when adjusting the dynamic NRT DCH scheduling target (PtxTargetPS) in downlink Cell level priority for both HSDPA and NRT DCH traffic type is determined by the dynamically adjusted cell level weight value (WeightHSDPA , WeightDCH)
Traffic Class
Interactive THP1 Interactive THP2 Interactive THP3 Background
HSDPA weight DCH weight value 0100 value 0100

100 75 50 25 90 65 40 15
WeightHSDPA is a structured management parameter including traffic class and THP separation (WeightHSDPATHP1, WeightHSDPATHP2, WeightHSDPATHP3, WeightHSDPABG) The same applies to WeightDCH parameter (WeightDCHTHP1, WeightDCHTHP2, WeightDCHTHP3, WeightDCHBG)
Figures in the table are default values
Prioritisation between HSDPA and DCH resources total weight calculated for user
A particular traffic class (THP) can be excluded in determination of weight values by setting the the traffic class (THP) specific weight value to 0 Cell level weight is obtained by summing the weight value of each user up
Weight of an individual user is an averaged weight of its NRT PS radio access bearers Weight of an individual user depends on the traffic class and traffic handling priority of its NRT PS radio access bearers
Whether user is included in the HSDPA traffic type or NRT DCH traffic type depends on its allocated transport channel (DCH or HS-DSCH) in downlink RT traffic, e.g. AMR speech CS RAB, has always higher priority to NRT DCH and HSDPA (HS-DSCH MAC-d flow) traffic
Prioritisation between HSDPA and DCH resourcestotal weight calculated for the cell
Weight of an individual user is an averaged weight of its NRT PS radio access bearers
Example1: (1 AMR+1 PS)
User1 with 1 AMR speech CS RAB + 1 PS RAB established (I/A THP2 HS-DSCH) WeightHSDPATHP2 = 90 Weight value of the User1 = 90 User2 with 2 PS RABs established (1 I/A THP1 DCH + 1 B/G DCH) WeightDCHTHP1 = 100, WeightDCHBG = 50 Weight value of the User2 = (100 + 50)/2 = 75
Example2: (2 PS, THP1 and BG))

Cell level weight is obtained by summing the weight value of each user up
Example3:
User1: HSDPA weight = 90, User2: DCH weight = 75, User3: HSDPA weight = 100, User4: DCH weight = 80, User5: DCH weight = 60 WeightHSDPA = User1+User3 = 190, WeightDCH = User2+User4+User5 = 215, WeightRatio = 215 / (215 + 190) = 0.53
Dynamic power allocation algorithm utilises WeightRatio
Weight Parameters in NEMU

RNC parameters
Module Contents
Dynamic HSDPA code allocation with HSDPA 15 codes feature Feature requirements for activation
Basic HSDPA HSDPA cell upgrade from 5 to 10 Codes HSDPA cell upgrade from 10 to 15 codes
HSDPA dynamic resource allocation Shared Scheduler for HSDPA BB efficiency

one WSPC per 3 cells in WBTS for HSDPA transmission WBTS licence
48 users per cell

one WSPC per cell needed
WBTS commissioning file
Shared Scheduler licence overrides the 48 users per cell feature if already activated
Maximum code allocation with HSUPA

Allocation of 15 is not possible when HSUPA is enabled in the cell
SF=1 SF=2 SF=4 SF=8 SF=16 SF=32 SF=64
Codes for common channels in the cell 14 HS-PDSCH codes
Codes for associated DCHs and non-HSDPA users
SF=128
SF=256
Up to three HSSCCH codes
E-AGCH (256)
E-RGCH/E-HICH (128)
Dynamic code allocation- code sets

The maximum code amount that can be used is 15 HS-PDSCH codes, but it is possible to get 10 codes also
HSDPA Dynamic Resource Allocation is activated/enabled (HSDPADynamicResourceAllocation management parameter)
If the maximum code value is 10, the recommended code set contains 5, 8 and 10 codes.
If the maximum code value is 15, the recommended code set contains 5, 8, 10, 12, 14 and 15 codes. The HSDPA Dynamic code allocation functionality is disabled by setting a code set that contains just 5 codes. WCEL parameters
Dynamic code allocation procedure

Initial allocation of HS-PDSCH codes (SF=16) is executed in the cell setup phase
The minimum number of HS-PDSCH codes is allocated initially
RNC attempts to upgrade HS-PDSCH codes

1) In conjunction of the HS-DSCH MAC-d flow setup
First setup will use the maximum available codes if possible (same conditions as in periodical case)
2) Periodically
RNC downgrades HS-PDSCH codes

1) Periodically 2) In the case of DPCH code congestion
RNC applies the timer HSPDSCHAdjustPeriod for periodical HS-PDSCH code adjustment
When the first HS-DSCH MAC-d flow is setup in the cell, RNC starts the timer Timer is used for periodical upgrade and downgrade of HS-PDSCH codes.
RNC shall stop the timer when the minimum allowed number of HS-PDSCH codes is allocated and there is(are) not any HS-DSCH MAC-d flow(s) setup in the cell.
HS-PDSCH code upgrade - Periodical

RNC periodically upgrades HS-PDSCH codes providing: 1. MAC-d exist already 2. The number of currently allocated HSPDSCH codes is lower than the maximum allowed number of HSPDSCH codes 3. BTS capability does not limit upgrade 4. Free SF=16 codes, which are adjacent to the currently allocated HS-PDSCH codes, can be found in order to take the next higher value from HS-PDSCH code set into use 5. Free SF=16 codes can be found so that after upgrade number of free SF=128 codes is greater than or equal to the value defined by the management parameter HSPDSCHMarginSF128 (def. 8) If the conditions for the periodical upgrade are effective, the next greater value from the HS-PDSCH code set is taken into use.
CodeN HS-PDSCH codes allocated in the code set HSPDSCHAdjustPeriod expires
CodeN < CodeMAX
Yes
Cell/BTS capable of CodeN+1 number of codes
Yes
No
Free SF#16 codes available for CodeN+1
Yes
Enough SF#128 codes available after upgrade
Yes
Keep the current number of HS-PDSCH codes

Take the value CodeN+1 from code set into use
HS-PDSCH code downgrade - Periodical

CodeN HS-PDSCH codes allocated in the code set
RNC periodically downgrades HSPDSCH codes providing:

1. Timer for periodical adjustment of the HS-PDSCH codes (HSPDSCHAdjustPeriod) expires 2. The number of currently allocated HS-PDSCH codes is higher than the minimum allowed number of HS-PDSCH codes 3. The number of currently available SF128 codes is lower than HSPDSCHMarginSF128 or there is(are) no HS-DSCH MAC-d flow(s) setup in the cell.
HSPDSCHAdjustPeriod expires
CodeN > CodeMIN
No
Yes
Available SF128 codes < HSPDSCHMarginSF128
No
Yes No HS-DSCH MAC-d flow(s) exists Yes
If the conditions determined above are effective, the next lower value from the HS-PDSCH code set is taken into use
Take the value CodeN-1 from code set into use
Keep the current number of HS-PDSCH codes
Code congestion
RNC downgrades HS-PDSCH code(s) due to DPCH code congestion
RNC does not downgrade HS-PDSCH codes lower than the minimum allowed number of HS-PDSCH codes
If RT request is congested due to lack of DPCH code(s), HS-PDSCH codes are downgraded in order to admit RT request If NRT DCH scheduling is congested due to lack of DPCH code(s), HS-PDSCH codes are downgraded in order to admit NRT DCH request
# HS-PDSCH codes > Maximum code set- DPCHOverHSPDSCHThreshold
The number of HS-PDSCH codes after downgrade will be the highest possible from the HS-PDSCH code set
HS-DSCH code downgrade Parameters

Number of reserved SF128 codes
128 118 108 98 88 78 68 58 48 38 0 15 14 13 12 11 10 9 8 7 6 5
HSPDSCHMarginSF128
Periodical HS-DSCH code downgrade if the number of currently available SF128 codes is lower than HSPDSCHMarginSF128 (default 8)
Number of allocated SF16 codes
HS-DSCH code downgrade due to NRT DCH code Maximum in congestion is allowed if code set number of currently allocated DPCHOverHSPDSCHThreshold HS-PDSCH codes is greater than Maximum code setDPCHOverHSPDSCHThresh old (default 0, no downgrade possible due to NRT congestion !!!)
Code tree optimisation

After upgrade of the HS-PDSCH codes triggering condition of the code tree optimisation procedure is checked Code change procedure tries to re-arrange the DPCH codes in order to make room for HS-PDSCH code upgrade If there are DPCH codes in the shared code area (HSDPA codes taken from SF 16), the following conditions and rules are checked each time a DPCH code is released:
1. Management parameter CodeTreeOptimisation is enabled in the cell 2. Number of currently allocated HS-PDSCH codes is lower than the maximum allowed number of HS-PDSCH codes 3. DPCHs having only SRB DCH are not allowed to be re-arranged 4. Code reallocation is done only if number of free HS-PDSCH code is increased
Dynamic Resource Allocation Parameters

WeightHSDPA
Range:1..100, step 1, Object:RNC Default: WeightHSDPATHP1=100, WeightHSDPATHP2=75, WeightHSDPATHP3=50, WeightHSDPABG=25)
WeightDCH
Range:1..100, step 1, Object:RNC Default: WeightDCHTHP1=90, WeightDCHTHP2=65, WeightDCHTHP3=40, WeightDCHBG=15
HSPDSCHCodeSet
Bitmask (16 bits, bit 5 = 5 codes enabled etc.), Default: with 5 codes 32 (bit 5 = 1), with 10 codes 1312, with 15 codes 54560
HSPDSCHAdjustPeriod
Range:1..60 s, step 1 s, Default:10 s, Object:RNC
HSPDSCHMarginSF128
Range and step: 0..128, step 1, Default value: 8, Object:WCEL
DPCHOverHSPDSCHThreshold
Range and step: 0..10, step 1 Default: 0, Object: WCEL
CodeTreeOptimisation
Range and step: 0 (Optimisation not used), 1 (Optimisation used) Default: 1, Object: WCEL
Example: HSDPA performance with 5 codes vs. 10 codes (Lab test- indoor environment with fading simulator)
Measurements in PedA 3km/h channel 10 codes provides higher throughput good signal quality as expected
50 % maximum gain , 25 % in average over measurement points
HSDPA throughput (PPP)

6000
HSDPA throughput (PPP)
5000
6000
Throughput / kbps
4000 5 codes max 10 codes ave 5 codes ave 2000

Throughput / kbps
5000
10 codes max 3000
4000 10 codes max 3000 5 codes max 10 codes ave 5 codes ave 2000
1000
1000
0 10 12 14 16 18 20 Reported CQI
0 -130
-120
-110
-100
-90
-80
RSCP / dBm
Example:Number of codes vs. PPP Throughput

The average number of codes remains high even with low RSCP values
Maximum 10 codes available Modulation is changed first to QPSK Number of codes is maximised by the link adaptation algorithm for maximum spectral efficiency
HSDPA number of codes
0.0 14 -20.0 12 -40.0 10 8 6 4 2 0 -60.0 -80.0 -100.0 -120.0 -140.0 avg. Codes RSCP
PPP throughput / bps
34
68
102
136
170
204
238
272
306
340
374
408
442
476
510
544
578
612
646
680
714
748
782
816
850
884
918
952
time / sec
986
Example: Used modulation 5 codes vs. 10 codes

RSCP drops
With 10 codes the modulation is switched 16-QAM QPSK prior to decreasing number of codes (you can see 5 or 10 codes in the picture but change of modulation)
HSDPA modulation - 10 codes

100% 80% 60% 40% 20% 0% 0 50 100 150 200 250 300 350 400 450 500 s QPSK 16-QAM NA 550 600 650 700 750 800 850 900 950
HSDPA modulation - 5 codes

100% 80% 60% 40% 20% 0% 0 50 100 150 200 250 300 350 400 450 500 s QPSK 16-QAM NA 550 600 650 700 750 800 850 900 950
Example: DL throughput 10 codes

Large variation on DL bit rate due to fading
Some packet drops also cause bit rate drop
DL PPP throughput
5000000 4500000 4000000 0.0 -20.0 -40.0 -60.0 -80.0 -100.0 -120.0 -140.0
3500000 3000000 2500000 2000000 1500000 1000000 500000 0
PPP DL RSCP
35
70
105
140
175
210
245
280
315
350
385
420
455
490
525
560
595
630
665
700
735
770
805
840
875
910
945
time / sec
980
Example: DL throughput 5 codes

Large variation on DL bit rate due to fading
Some packet drops also cause bit rate drop
DL PPP throughput
5000000 4500000 4000000 0.0 -20.0 -40.0 -60.0 -80.0 -100.0 -120.0 -140.0
3500000 3000000 2500000 2000000 1500000 1000000 500000 0
PPP DL RSCP
35
70
105
140
175
210
245
280
315
350
385
420
455
490
525
560
595
630
665
700
735
770
805
840
875
910
945
time / sec
980
Module Contents
RAS06 main features
HSUPA resource Handling Enhanced HSDPA mobility handling
HSDPA Code Multiplexing

Optional feature HSDPA Code Multiplexing enables simultaneous transmission of (max) three HSDPA users within a single cell during a single Transmission Time Interval (TTI)
HSDPA Code Multiplexing is activated in RNC by giving to cell level RNP parameter MaxNbrOfHSSCCHCodes value that is bigger than 1
Each multiplexed HSDPA user needs own HS-SCCH code
This feature can not be used without HSDPA 15 Codes feature

Nokia RAN uses at least 3 HS-PDSCH codes per one multiplexed HSDPA user
HSDPA 10 Mbps per User

It is possible to increase the user throughput by separate licenced feature This will be activated in RNC by changing the parameter
Maximum bitrate of NRT MAC-d flow from default 6784 kbps 9600 kbps
This is default for 7.2 Mbps
48 simultaneous HSDPA users per cell

This licenced feature enables 48 simultaneous HSDPA users in one cell
Maximum number of HSDPA users depends on also configuration of BTS
Depending on activated features and BTS configuration the maximum is

16 per cell group (1-3 cells) 16 per cell 48 per cell group (1-3 cells) 48 per cell
A cell group builds up from those cells that are controlled by same MAC-HS scheduler in BTS HSDPA 48 Users per Cell is activated with the RNC level RNP parameter HSDPA48UsersEnabled Sensible Iub and BTS baseband dimensioning requires that also feature 16 kbit/s Return Channel DCH Data Rate Support for HSDPA is in use + corresponding other HSDPA bitrate parameters
Parameters
MaxNbrOfHSSCCHCodes
Range and step: 1..3, step 1, Default value: 1, Object:WCEL
HSDPA48UsersEnabled
Range and step: 0 (Not in use), 1 (In use) Default value: 0, Object:RNC
HSDPA16KBPSReturnChannel
Range and step: 0 (Disabled), 1 (Enabled) Default value: 0, Object:RNC
HSDPAminAllowedBitrateUL
Range and step: 1 (16 kbps), 3 (64 kbps), 4 (128 kbps), 6 (384 kbps) Default 3, Object: RNC
HSDPAinitialBitrateUL
Range and step: 1 (16 kbps), 3 (64 kbps), 4 (128 kbps), 6 (384 kbps) Default 3, Object: RNC
Parameters in NEMU
RNC Parameters
Example-Test cases
No code mux
2 HSPA, Cat. 8 (10 codes) 1 HSDPA, Cat 6 (5 codes)
Code mux, 3 HS-SCCH

2 HSPA, Cat. 8 1 HSDPA, Cat 6 13 codes available for HSDPA
Code mux, 2 HS-SCCH (0 margin for DCH codes)

2 HSPA, Cat. 8 14 codes available for HSDPA
Example-Cell throughput
Maximum achieved cell throughput 8.7 Mbit/s Code multiplexing increases cell throughput by 40%
Cat 8 UEs are multiplexed to same TTI
Transport channel throughput
10000 9000 8000 7000 6000 5896 No mux 4340 3669 2460 4363 3521 2442 9931135 1000 0 Cat 8 - 1 Cat 8 - 2 UE type, Cell Cat 6 Cell Code Mux 3-HS-SCCH Code Mux 2-HS-SCCH 8704 8325
kbit/s
5000 4000 3000 2000
Example-Max cell throughput with code mux

Theoretically maximum cell throughput of 14.05 Mbps (MAC-hs) is achieved with code multiplexing of 2 UEs (8 + 7 codes)
TB size 14936 & 13177
Measurement result indicates average achieved TB size is less than 10900 Maximum cell throughput can not be achieved in used conditions
Final TBS
16000.0 14155.0 14000.0 12000.0 10000.0 8000.0 6000.0 4000.0 2000.0 0.0 0.0 Cat 8 - 1 Cat 8 - 2 UE type Cat 6 10264.5 9616.7 13904.0
10873.6 9585.2 No mux 6898.3 6446.1 Code Mux 3-HS-SCCH Code Mux 2-HS-SCCH
Scheduling example 3 HS-SCCH codes

3 UEs used 13 codes divided to 2 UEs (no codes allocated for 3rd UE)
6 (Cat-8) + 7 (Cat-8) or 8 (Cat-8) + 5 (Cat-6)
Available power (15.7 W) divided equally to 2 UEs

UE cat. User No CQI Comp. Modulation CQI No of PDSCH codes Final TBS PDSCH power (dBm)
8 8 6 8 8 8 -
36866 36865 36867 36865 36866 36865 -
23 23 23 23 23 22 -
25 24 27 24 25 24 -
16QAM 16QAM 16QAM 16QAM 16QAM 16QAM -
7 6 5 8 7 6 -
10821 8574 7168 10629 10821 8574 -
38.968 38.968 38.964 38.964 38.97 38.97 -
Module Contents
RAS06 main features
HSUPA resource Handling Enhanced HSDPA mobility handling
HSDPA associated uplink DPCH channel

When the radio bearer is mapped onto HS-DSCH transport channel in downlink, either E-DCH or DCH is allocated in uplink as a return channel Supported data rates for UL DCH return channel are 16, 64, 128 and 384 kbit/s
16 kbps UL DCH return channel is an optional feature, which can be activated by the operator with the management parameter HSDPA16KBPSReturnChannel Minimum allowed bit rate with HSDPAminAllowedBitrateUL parameter Not limited by BitRateSetPSNRT
PS: HS-DSCH (DL)
PS: DCH (UL)
HSDPA associated uplink DPCH scheduling

If the HS-DSCH allocation is triggered by uplink, normal NRT DCH scheduling rules are applied
If the traffic volume measurement indicates High traffic volume, the RNC attempts to allocate a return channel with the highest possible bit rate
TrafVolThresholdULHigh parameter
If the traffic volume measurement indicates Low traffic volume, the RNC attempts to allocate a return channel with configured initial bit rate
HSDPAinitialBitrateUL parameter
If the HS-DSCH allocation is triggered by downlink, the RNC attempts to allocate the uplink with the HSDPAinitialBitrateUL parameter In the case of direct DCH to HS-DSCH switch, the HSDPA UL DCH bit rate can be same as existing DCH UL bit rate If even initial bit rate or higher can not be allocated, HS-DSCH allocation is not possible
DL/UL DCH is scheduled to the UE
HSDPA associated uplink DPCH scheduling

The following existing functionalities are applied to the HSDPA-associated UL DCH:
Priority-based scheduling and overload control
Decrease of the retried NRT DCH bit rate

RT-over-NRT Throughput-based optimisation Upgrade of NRT DCH Data Rate (Normal or Flexible upgrade)
Throughput-based optimisation and Flexible upgrade can be disabled for HSDPA associated uplink DPCH with DynUsageHSDPAReturnChannel
Example use case 1: HSDPA UL DCH with initial bit rate 64 kbps
The initial bit rate (HSDPAinitialBitrateUL) is set to 64 kbps. The minimum bit rate is set to 16 kbps (HSDPAminAllowedBitrateUL)
kbps 384 Decrease of the retried NRT DCH bitrate
Priority based scheduling/ RT-over-NRT
128 Initial bitrate 64 kbps 64 Minimum bitrate 16 kbps t t1 Capacity Request (Traf.vol measurement low)
16 0 t2 Capacity Request (Traf.vol measurement high) t3 t4 t5
Capacity Request (Traf.vol measurement high)
Example use case 2: Initial bit rate 128 kbps
Example- DL performance with 16 kbits/s return channel

DL average throughput was limited 878 kbit/s
Max. 1.077 Mbit/s TTI reservation 46% Average TB size 5100 bits (min 4400, max 6400)
PPP throughput - DL
1200000
1000000
800000
600000
400000
200000
20
40
60
80
100
120
140
160
180
200
220
240
260
280
300
320
340
360
380
400
420
440
460
480
500
520
540
560
580
600
620
640
660
680
700
720
time
740
Parameters
HSDPA16KBPSReturnChannel
Range and step: 0 (Disabled), 1 (Enabled), Default value: 0, Object:RNC
HSDPAminAllowedBitrateUL
Range and step: 1 (16 kbps), 3 (64 kbps), 4 (128 kbps), 6 (384 kbps), Default value: 3 , Object:RNC
BitRateSetPSNRT
Range and step: 0 (Predefined bit rate set is not in use = All supported bit rates are in use), 1 (Predefined bit rate set is in use), Default value: 0, Object:RNC
TrafVolThresholdULHigh
Range and step: 0 (8 bytes), 1 (16 bytes), 2 (32 bytes), 3 (64 bytes), 4 (128 bytes), 5 (256 bytes), 6 (512 bytes), 7 (1024 bytes. 1 KB), 8 (2048 bytes. 2 KB), 9 (3072 bytes. 3 KB), 10 (4096 bytes. 4 KB), 11 (6144 bytes. 6 KB), 12 (8192 bytes. 8KB), 13 (12288 bytes. 12 KB), 14 (16384 bytes. 16 KB), 15 (24576 bytes. 24 KB), Default value: 7, Object:RNC
TrafVolThresholdULLow
Range and step: 8 (8 bytes), 16 (16 bytes), 32 (32 bytes), 64 (64 bytes), 128 (128 bytes), 256 (256 bytes), 512 (512 bytes), 1024 (1 KB) Default value: 128, Object:RNC
HSDPAinitialBitrateUL
Range and step: 1 (16 kbps), 3 (64 kbps), 4 (128 kbps), 6 (384 kbps), Default value: 3, Object:RNC
DynUsageHSDPAReturnChannel
Range and step: 0 (Off), 1 (On), Default value: 0, Object:RNC
Parameters in NEMU
Module Contents
RAS06 main features HSDPA resource handling HSUPA resource Handling HSUPA Overview HSUPA Packet Scheduling HSUPA Mobility HSUPA Release Basic Signalling Ue Capability Transport Block size Happy Bit
HSUPA - General principle

E-DPDCH + E-DPCCH (scheduling request)
HSUPA UE
E-AGCH (Grant allowed power) E-DPDCH (data)+ E-DPCCH(ctrl ch (bit) E-HICH (Ack/Nack, Layer1) E-RGCH (Granting more or less power, or hold)
Serving cell
Node B completes scheduling based on happy bit and cell load Node B grants the E-DPDCH transmit power ratio each UE is allowed to use UE selects the highest bit rate that it is allowed according the granted power and the allowed Transport Format Combination Set (TFCS) UE is allowed to use the scheduled bit rate until receiving the next grant
SHO is supported. Non serving cell can only send down/hold power commands.
Cell in active set
E-DCH Transport Block Sizes
RAS06 supports 10 ms TTI and Transport Block (TB) size table 1

This table is optimised by 3GPP for RLC PDU sizes of 336 and 656 bits The UE must select an appropriate TB size from this table as part of E-TFC selection Example RLC throughput calculation based upon this table
Maximum transport block size = 19950 bits MAC-e/es header = 18 bits
=> maximum number of RLC PDU = (19950-18)/336=59

Typical RLC payload = 320 bits RLC throughput = 320 * 59 / 0.01 = 1.888 Mbps
TB Indices of 0, 1 and 2 are not possible because they are unable to accommodate 1 RLC PDU
UE Capability
Category 5 HSUPA UE limits the maximum TB size to 20000 (10 ms TTI) Can potentially select a TB index from 0 to 120
Happy Bit
Happy Bit forms input for MAC-e scheduler Happy bit is included as part of E-DPCCH The Happy Bit Delay Condition defines the duration over which to evaluate the current grant relative to the total buffer status The happy bit is set to unhappy if all 3 of the following are true:
UE is transmitting as much scheduled data as allowed by the current serving grant UE has sufficient power available to transmit at a higher data rate Based upon the same power offsets as used for that TTI, the total buffer status would require more than Happy Bit Delay Condition ms to be sent with the current serving grant * active HARQ processes / total HARQ processes Always equal to 1 for 10 ms TTI
Parameter HappyBitDelayConditionEDCH
Scope RNC
Range 2, 10, 20, 50, 100, 200, 500, 1000 ms
Default 50 ms
This parameter determines the value for the Happy Bit Delay Condition. This information element is signalled to the UE usin g the RRC protocol. The UE uses this parameter to help set the happy bit.
Module Contents
RAS06 main features HSDPA resource handling HSUPA resource Handling
HSUPA Overview HSUPA Packet Scheduling HSUPA Mobility HSUPA Release
HSUPA Requirements & Parameters

Feature requirements:
HSDPA Basic HSDPA, RAN763 HSDPA Serving cell change feature, RAN828 HSDPA Dynamic resource allocation, RAN312 When basic HSUPA and HSUPA basic RRM are active, also HSUPA handover and HSUPA BTS packet scheduler become automatically available Parameter requirements:
Definition of HSPA FMCS_id if ADJS are present for the WCEL (same of FMCx of HSDPA could be initially used)
Parameter HSUPAEnabled set to "enabled"

This action require cell locking HSUPA must be activated in all the cells under the same frequency in the same nodeB: there cannot be cells with HSUPA and cells without HSUPA under the same frequency in the same node-B
HSUPA Requirements & Parameters

The EDCHQOSClasses parameter can be used to select which traffic classes are able to use HSUPA.
This parameter must be configured to be consistent with the equivalent HSDPA parameter (HSDSCHQoSclasses).
Max number of HSUPA connections

per cell (MaxNumberEDCHCell, max 20) per logical cell group (MaxNumberEDCHLCG, max 24).
It is also possible to reserve a subset of the total number of connections for HSUPA soft handover (NumberEDCHReservedSHOBranchAdditions)
The MaxTotalUplinkSymbolRate (wrong name,should be bitrate!)parameter defines the maximum symbol rate per HSDPA connection.
3840 kbps for RAN979 HSUPA 2.0 Mbps
1920 kbps for maximum bit rate of 1.44 Mbps.

Node B scheduler shares resources between UE with HSUPA connections
RNC scheduler continues to manage R99 DCH connections

Similar to HSDPA scheduler in MAC-hs, HSUPA scheduler in MAC-e is faster than an RNC scheduler HSUPA throughput is controlled with absolute and relative grants Scheduling period is 10 ms
RNC 384 256 128 64 1. Node B 384 256 128 64 32 16 8 Zero Grant 2. UE 384 256 128 64 32 16 8 Zero Grant 4. 3.
1. 2.
RNC limits the E-TFCI based upon UE capability and QoS profile Node B limits E-TFCI based upon packet scheduling principles
32
16 8 Zero Grant
3.
4.
UE limits E-TFCI based upon transmit power capability

UE selects E-TFCI based upon data to be transferred

HSUPA scheduler combines throughput and load based algorithms
Throughput based scheduling is applied for lower loads
Power based scheduling is applied for higher loads Scheduler uses absolute and relative grants to maximise the utilisation of every user and minimise the difference between the requested and allocated bit rates Scheduling decisions are based on the
Uplink interference margin Physical layer feedback (happy bit)
Prx RNC PS DCH scheduling domain
Throughput-based
Power-based PrxMaxTargetBTS
Iub capacity
Available baseband processing capacity
PrxLoadMarginEDCH
Minimum Throughput for E-DCH scheduling in BTS

BTS does not do any power estimations and interference threshold checkings until own cell load (for DCH and E-DCH) is higher than minimum UL own cell load factor
Node B Scheduling Procedure

PS NRT DCH (R99) users and HSPA users share the same interference power resource which is left over from the RT DCH users. PrxTarget is used when there are no E-DCH connection with the cell. Dynamic target Prx_Target_PS is used when one or more E-DCH connections have been established.
Prx_Target_PS is applicable to NRT scheduling and can be adjusted between PrxTargetPSMax and PrxTargetPSMin.
RT admission control continues to use PrxTarget
No HSUPA users HSUPA active No HSUPA users PrxMaxTargetBTS PrxTarget PrxTargetPSMax PrxEDCH Prx_Target_PS PrxTargetPSMin
Prx_Target_PS is applicable to NRT scheduling and can be adjusted between PrxTargetPSMax and PrxTargetPSMin
PrxNRT
PrxNC
Node B Scheduling Procedure (Initial Conditions)

RNC sends PrxMaxTargetBTS and Lmincell to the Node B Node B calculates the maximum target load from PrxTarget BTS
Lmincell (from RNC)
-95 -96
Max Cell Load (Calculated from PrxMaxTargetBTS)
Throughput based
-97 -98
Power based PrxMaxTargetBTS (from RNC)
RTWP (dBm)
-99 -100 -101 -102 -103 -104 -105 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1
OwnLoad Cell Load

Node B Scheduling Procedure (Throughput Based)

Node B calculates the own cell load If calculated own cell load is less than Lmincell then throughput based scheduling can be applied to increase the own cell load to Lmincell
Calculated Own Cell Load
-95 -96 -97 -98
Lmincell (from RNC)
Max Cell Load (Calculated from PrxMaxTarget)
RTWP (dBm)
-99 -100 -101 -102 -103 -104 -105 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1
PrxMaxTargetBTS (from RNC) Schedule Resource
OwnLoad Cell Load

Node B Scheduling Procedure (Power Based I)

If calculated own cell load is greater than Lmincell then power based scheduling is applied to increase the total cell load to Max Cell Load
Calculated Own Cell Load Lmincell (from RNC)
-95 -96 -97 -98
Max Cell Load (Calculated from PrxMaxTarget)
RTWP (dBm)
-99 -100 -101 -102 -103 -104 -105 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1
PrxMaxTargetBTS (from RNC)
OwnLoad Cell Load

Node B Scheduling Procedure (Power Based II)

Node B measures actual RTWP and calculates the actual load
Calculated Own Cell Load Lmincell (from RNC)
-95 -96 -97 -98
Calculated Total Cell Load Max Cell Load (Calculated from PrxMaxTarget)
RTWP (dBm)
-99 -100 -101 -102 -103 -104 -105 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1
PrxMaxTargetBTS (from RNC)
Schedule Resource
Measured RTWP (Received Total Wideband Power)
OwnLoad Cell Load

Parameters for Node B Scheduling (I)

Parameter PrxMaxTargetBTS
Scope WCEL Range 0 to 30, step 0.1 dB Default 6 dB
The maximum target for received total wide band power in the cell for BTS packet scheduling. The value of the PrxMaxTargetBTS is relative to the system noise. It gives an upper threshold for the noise rise: the ratio of the total received uplink power to system noise
This parameter is transferred from the RNC to the Node B using the NBAP Physical Shared Channel Reconfiguration Request message The information element used within this message is:
An absolute value is signalled so the value has to be updated if PrxNoise changes It is suggested to configure this parameter to be greater than PrxTarget + PrxOffset because the Node B is more responsive than the RNC
Parameters for Node B Scheduling (II)

Parameter PrxNoise
Scope WCEL Range -130 to -50, step 0.1 dBm Default -101.9 dBm
Defines the noise level in the BTS digital receiver when there is no load (thermal noise + noise figure). This parameter is required for noise rise calculations.
This parameter is transferred from the RNC to the Node B using the NBAP Physical Shared Channel Reconfiguration Request message The information element used within this message is:
If PrxNoise changes as a result of auto-tuning or a parameter change then the Node B is informed of the change
Parameters for Node B Scheduling (III)

Parameter PrxLoadMarginEDCH
Scope WCEL Range 0 to 30, step 0.1 dB Default 2 dB
Defines the own cell uplink load (DCH and E-DCH) threshold used to trigger the use of power based scheduling. Throughput based scheduling is used when the own cell load is below this threshold.
Default PrxLoadMarginEDCH of 2 dB corresponds to a load of 37 % Configuring a value of 0 dB makes the scheduler completely power based The following calculation is completed by the RNC to translate the noise rise to an uplink cell load:
LminCELL 1
Prx _ noise Prx _ noise Pr xLoadM arg inEDCH
Private NBAP message is used to transfer LminCELL to the Node B
Downlink Physical Channels-Transmit Power Parameters

Parameter PtxOffsetEHICH
Scope WCEL Range -32 to 31.75, step 0.25 dB Default -11 dB
Transmission power of the E-HICH. E-HICH power is relative to the transmission power of primary CPICH.
Parameter
Scope
Range -32 to 31.75, step 0.25 dB
Default -5 dB
PtxOffsetEAGCH WCEL
Transmission power of the E-AGCH. E-AGCH power is relative to the transmission power of primary CPICH.
Parameter
Scope
Range -32 to 31.75, step 0.25 dB
Default -11 dB
PtxOffsetERGCH WCEL
Transmission power of the E-RGCH. E-RGCH power is relative to the transmission power of primary CPICH.
Serving Grant Calculation

HSUPA power is adjusted based on Serving Grant info send to the Ue (E-DPDCH to DPCCH power) Mapping between kbps figure and Serving Grant Value done in Node B
Initial bitrate of 32 kbps used with radio bearer reconfiguration message which is send to Ue (no E-AGCH or E-RGCH used here)
The E-AGCH can rapidly increase the bit rate if UE is unhappy (single Ue in the cell) With many UEs is the cell the E-RGCH is used to increase the power (the data buffer is full in UE and there is capacity in Node B)
Step size 1
One upgrade per scheduling period (10ms) E-RGCH used to send the down command (happy or congestion) One downgrade per scheduling period (10ms)
Step size 1
Fast Ramp-Up of Bit Rate

The E-AGCH can rapidly increase the bit rate allocated to a UE This is applicable if there is a single modifiable UE which is unhappy The UE bit rate is not allowed to increase while the PS Upgrade Timer (Tup) is running Node B attempts to assign the available resources to that UE using the E-AGCH
Non-Configurable Tup
Default 50 ms
The period during which a UE grant is not allowed to increase
Scheduling Procedure (I)

The scheduling procedure is completed every 10 ms
Handling non-serving cell overload
The scheduler shall transmit the Down grant to UE whose serving E-DCH RL is not provided by that Node-B if the following criteria are true:
RTWP Measured > Max. Target RTWP
Non-serving E-DCH to Total E-DCH Power Ratio > Target Ratio
E-RGCH used to send the down command

Parameter TargetNSEDCHToTotalEDCHPR
Scope Range 0 to 100, step 1 % Default 50 %
WCEL
This parameter defines the target ratio of the power from UEs for which this cell is a non-serving radio link and the total received E-DCH power. If this target is exceeded and also the experienced total RTWP is higher than the target RTWP signalled from the CRNC, the BTS is allowed to send to a non-serving radio link RG Down command. Information is signalled to the BTS using the NBAP: Target Non-serving E-DCH to Total E-DCH Power Ratio information element.
Scheduling Procedure
The load of the serving and non serving cell should not be too high Iub congestion should not be too high (Delay Build-up or Frame Loss) Ue uses lower grant than allocated by Node B
Handling non-serving cell overload
Handling congestion indicators
Handling Low Utilisation UE
Lrx_EDCH_Allowed = Max(Lrx_EDCH_Power, Lrx_EDCH_Throughput)
Calculate the maximum of the load increases allowed by the throughput and power based thresholds If either is positive then the E-DCH load can be increased Otherwise, the E-DCH load is decreased
Lrx_EDCH_Allowed > 0 Yes Load increase estimation No Load decrease estimation
Allocate Grant
Allocate Grant
Load Increase Estimation

Yes
Fast Ramp-Up Procedure No Exit Single Modifiable unhappy UE? No
Modifiable unhappy UE Exists? Yes Load increase estimation Increase the bit rate of the modifiable unhappy UE using the E-RGCH Yes Sufficient margin to allow an increase No Yes Hardware resources available?
No
Load Decrease Estimation
No Exit
Load remains above Target? Yes
No Exit
Active E-DCH Exists? Yes Decrease the UE bit rate using the E-RGCH
Load decrease estimation
Other Scheduling Mechanisms

All of the following mechanisms use the E-AGCH
The following scenarios result in a decrease of the allocated grant

If a UE is detected to be using DTX If a UE is received with very poor quality If a UE is detected to be using more than its allocated grant If there is a limitation in terms of Node B processing resources
PedA 3 km/h HSUPA SG and AG -example

Pathloss increase
With low pathloss the HSUPA bit rate is limited by grant
Limitation of HSUPA data rate 100% 80% 60% 40% 20% 0% 0 50 100 150 200 250 300 350 400 450 500 550 600 650 700 750 800 850 900 950 s
When pathloss increases the UE transmit power starts limiting

No other traffic so the serving grant is at maximum Grant is decreased when UE can not use the given grant low utilisation
SG, AG
Pow er
Grant
Data
HSUPA - SG & AG
30 25 20 15 10 5 0 SG AG
51 10 2 15 3
20 4 25 5 30 6 35 7 40 8 45 9 51 0 56 1 61 2 66 3 71 4 76 5 81 6 86 7
tim e
10 20 10 71 11 22 11 73 12 24 12 75 13 26 13 77 14 28 14 79
91 8 96 9
Examples-HSUPA data rate Limitation

Limitation of HSUPA data rate 100% Power Grant Data
80%
This picture shows what was the limiting factor of the throughput during the data transfer. Grant 92% of time Data 6% of time UL Power 1% o time Data means that Ue had
empty buffer no new data to send
60%
40%
20%
At low RSCP more samples with UL Power limitation But also a bit more Data limitation, most likely is caused by the UL power limitation caused TCP/IP congestion control to kick in
0 50 100 150 200 250 300 350 400 450 500 550 600 650 700 750 800 850 900 950 s
0%
Examples-Average HSUPA TB Size
average HSUPA TB size 25000
The TB size was most of the time 20000

Some variation clearly visible during the lower RSCP.
20000
15000
bit
10000 5000
0 0 50 100 150 200 250 300 350 400 450 500 550 600 650 700 750 800 850 900 950 s
Examples-SG and AG Relative to RSCP

From the graph below it can bee seen that at low RSCP the UE tx power is increased as well as there are more Absolute Grants given to the terminal at lower RSCP This can be explained by the fact that the terminal power control does not necessarily always follow the sudden power changes related to high throughput at cell edge causing some increased interference spikes at the BTS
This in turn causes the BTS to reduce aggressively (fast with big change) the throughput and therefore Absolute Grants are used (providing absolute limit for throughput without any limit of change
This can be seen as greater fluctuation of throughput at lower RSCP

SGRANT
30
UETXP
AGRANT as SG
Measured MACe tput [mbps]*10
At high RSCP the absolute grant is seldom used and therefore also the throughput is having less fluctuation compared to low RSCP
20
10
0 -85 -80 -75 -70 -65 -60 -55 -50 -45 -40
-10
-20
-30
-40 RSCP [dBm]
Happy Bit & Grant Type

0 1 2 3 4 5 6 7 8 9
Grant Type: 3 = Downgrade by RGCH 2 = 10 Upgrade by RGCH 1 = Upgrade/Downgrade by AGCH
Happy bit
Grant Type
HSUPA Throughput Test Analysis Downgrades and Upgrades
SFN 0 20 40
Allocated E-TFCI
2332 2342 2352 2362 2372 2382 2392 2402 2412 2422 2432 2442 2452 2462 2472 2482 2492 2502 2512 2522 2532 2542 2552 2562 2572 2582 2592 2602 2612 2622 2632 2642 2652 2662 2672 2682 2692 2702 2712 2722 2732 2742 2752 2762 2772 2782 2792 2802 2812 2822 2832 2842 2852 2862 2872 2882 2892 2902 2912 2922 2932 2942 2952 2962 2972 2982 2992 3002 3012 3022 3032 3042 3052 3062 3072 3082
60 80 100 120 140
E-TFCI
Module Contents
HSUPA Mobility
Intra-frequency mobility allows soft and softer handovers
Separate reservation of E-DCH allocations (for soft/softer ho) are made using the NumberEDCHReservedSHOBranchAdditions
Inter-frequency and inter-system mobility is provided via DCH in the same way as for HSDPA E-DCH serving cell is always the same as HS-DSCH serving cell HS-DSCH serving cell change and HS-DSCH serving cell selection algorithms are not changed due to HSUPA
It is more critical for HSDPA than for HSUPA that the serving cell is the best cell as HSDPA does not have soft handover like in HSUPA
The cell which cannot be added to E-DCH active set should not cause problems-> Quality triggers
E-DCH Active Set

E-DCH active set is a subset of the DCH active set Maximum number of cells in E-DCH active set is 3 (same as for DCH) Cells can be left out from the E-DCH active set but included within the DCH active set due to: HSUPA is not enabled for the cell (HSUPAEnabled) The cell belongs to a DRNC (E-DCH over Iur is not supported) The maximum number of E-DCH users is reached for that cell or BTS local cell group There are no free E-DCH resources within the BTS local cell group The active set can contain both softer and soft handover radio links The E-DCH and DCH active sets have to be identical in softer handover The E-DCH and DCH active sets can be different for soft handover and so cells can be added only to the DCH active set The cell shall be added to the E-DCH active set later if possible by using internal retry timer(Minimum(10 s, NUMBER OF FAILS * 2 s))
Measurement reporting and Serving HS-DSCH Cell Change

Event 1A 1B 1C Description A primary CPICH enters the reporting range. A primary CPICH (Serving HS-DSCH cell) leaves the reporting range. A non-active primary CPICH becomes better than an active (Serving HS-DSCH cell) one UE Rx-Tx time difference for a RL included in the active set becomes larger than an absolute threshold A primary CPICH goes below the absolute threshold. UE Tx power exceeds the absolute threshold. Uplink quality deterioration report (in RNC) DL transmitted code power > limit Actions on HSDPA Start HSDPA specific measurements Trigger for serving HS-DSCH cell change Trigger for serving HS-DSCH cell change
6F/6G
Trigger for serving HS-DSCH cell change
1F
Trigger for releasing the HS-DSCH MAC-d flow (after 1F for all AS cells) + for AMR multi-RAB inter-frequency/-RAT measurements Trigger for releasing the HS-DSCH MAC-d flow + for AMR multi-RAB inter-frequency/-RAT measurements Trigger for releasing the HS-DSCH MAC-d flow Trigger for releasing the HS-DSCH MAC-d flow + for AMR multi-RAB inter-frequency/-RAT measurements
6A
HS-DSCH SCC change, E-DCH selected or not ?

When HS-DSCH serving cell change is triggered, it is checked if DCH <-> E-DCH channel type switch is required
DCH allocated in the UL

RNC checks if E-DCH can be selected
Serving cell must support E-DCH Non-serving cells in DCH active set which cannot be added to the E-DCH active set must not have too high CPICH Ec/Io reported by the UE
E-DCH allocated in the UL RNC checks if E-DCH can be maintained

Serving cell must support E-DCH Non-serving cells in DCH active set which cannot be added to the E-DCH active set must not have too high CPICH Ec/Io reported by the UE
Non-E-DCH area E-DCH area
Non-E-DCH area
HSUPA mobility quality triggers

HSUPA should be enabled in all cells in Node B UE can have an active set which includes both E-DCH and DCH cells
The DCH cells can trigger E-DCH to DCH channel type switching to DCH cells are unable to control the E-DPDCH transmit power because they are not configured with the E-RGCH
EDCHRemEcNoOffset defines a window above the CPICH Ec/Io of the HSUPA serving cell (default 2 dB) EDCHCTSwitchGuardTimer parameter defines a time window during which channel type switching from DCH to EDCH is disallowed after a switch from E-DCH to DCH (default 2s)
HSUPA mobility quality triggers

If the initial channel allocation (initial channel type selection between DCH and EDCH), or channel type switch from DCH to E-DCH, the E-DCH cannot be allocated, because the E-DCH active set is not acceptable, the RNC starts to follow if E-DCH active set changes to acceptable E-DCH active set can change to acceptable if the cell which is not in E-DCH active becomes weak enough or is removed from the DCH active set.
EDCHAddEcNoOffset parameter defines a window below the CPICH Ec/Io of the HSDPA serving cell (default 0 dB)
Parameter sets in soft handover

The WCEL:HSPAFmcsidentifier is used when a single NRT PS RAB is establsihed having HS_DSCH and E-DCH transport channel allocated The optional feature RAN974 allows a CS speech connection to be established simultaneously with an HSUPA PS data connection. The RNC:AMRwithEDCH parameter activates this capability if the optional feature has been enabled. The WCEL: RTWithHSPAFmcsIdentifier is used when AMR speech CS RAB is established simultaneously with an NRT PS RAB having HS-DSCH and E-DCH transport channel allocated.
Tput (Mbps)
1000000
1500000
2000000
2500000
500000
HSUPA Throughput during SCC- example
2nd cell added to active set
Gap ~600ms
Throughput vs. time
Time
1st cell dropped from active set
MACTPUTUL
GRANTEDTPUT
7: 56 :4 7: 3 56 :4 7: 3 56 :4 7: 4 56 :4 7: 4 56 :4 7: 5 56 :4 7: 5 56 :4 7: 6 56 :4 7: 7 56 :4 7: 7 56 :4 7: 8 56 :4 7: 8 56 :4 7: 9 56 :4 7: 9 56 :5 7: 0 56 :5 7: 1 56 :5 7: 1 56 :5 7: 2 56 :5 7: 2 56 :5 7: 3 56 :5 7: 3 56 :5 7: 4 56 :5 7: 4 56 :5 5
Inter-RNC HSPA Cell Change, Effect on User Plane

Without Inter-RNC HSPA Cell Change
With Inter-RNC HSPA Cell Change
on a DCH, in this case only one second on a 64/64, actual user plane break in this case ~4.5 s
Relocation triggered
HHO relocation triggered
HSPA to DCH switch
DCH to HSPA switch
2,5Mbit/s
Implementation at RAS06 E4: HSPA service is switched to DCH at the RNC border area
Implementation with Inter-RNC HSPA CC: Improved end user experience, HSPA high data rates can be maintained in RNC border areas User plane data break in average= 1.4 seconds
Module Contents
E-DCH Connection Release (I)

Low throughput is used to trigger a release of the E-DCH The MAC layer within the RNC is responsible for monitoring throughput EDCHMACdFlowThroughputAveWin defines a sliding window for the throughput measurement
Measurement window is moved every TTI

Throughput is calculated every TTI Measurement window has to be full of samples before the first throughput measurement result is calculated If the first activity of a MAC-d flow is not detected within (EDCHMACdFlowThroughputAveWin + 2 s), the MAC layer sends a low throughput indication to layer 3
E-DCH Connection Release (II)

Timer is started if throughput EDCHMACdFlowThroughputRelThr Timer is stopped and reset if throughput returns above EDCHMACdFlowThroughputRelThr Low throughput indication is sent if timer reaches EDCHMACdFlowThroughputTimetoTrigger If EDCHMACdFlowThroughputTimetoTrigger = 0 then low throughput indication is sent immediately If the low throughput indication has been sent and throughput returns above threshold then normal throughput indication is sent to layer 3
Throughput Result EDCHMACdFlowThroughputAveWin Low throughput indication sent to layer 3 TTI EDCHMACdFlowThroughputRelThr Normal throughput indication sent to layer 3
EDCHMACdFlowThroughputTimetoTrigger
E-DCH Connection Release (III)

E-DCH is not necessarily released as soon as the low throughput indication is sent because the release also depends upon HS-DSCH throughput and utilisation Layer 3 starts to release downlink HS-DSCH and corresponding E-DCH if: Or HS-DSCH MAC-d flow has low throughput and E-DCH can be released. In this case UE specific timer HsdschGuardTimerLowThroughput is started HS-DSCH MAC-d flow has low utilization and E-DCH can be released as a result of low throughput
Low utilisation measurement is not applicable to E-DCH because the RNC does not have visibility of the uplink transmit buffer occupancy (Node B quantifies E-DCH utilisation by measuring activity on the E-DPDCH)
Parameters for E-DCH Release (I)

Parameter EDCHMACdFlowThroughputRelThr
Scope RNC Range 0 to 64000, step 256 bps Default 256 bps
This parameter defines the low throughput threshold for the throughput measurement of the E-DCH NRT MAC-d flow. The threshold is defined as a number of bits per second. The throughput measurement measures the number of bits transmitted by E-DCH NRT MAC-d flow during the sliding measurement window. The sliding measurement window is defined with the parameter EDCHMACdFlowThroughputAveWin. If the result of the throughput measurement is less than or equal to the threshold the EDCHMACdFlowThroughputTimetoTrigger timer is started .
Parameter EDCHMACdFlowThroughputTimetoTrigger
Scope RNC
Range 0 to 300, step 0.2 s
Default 5 s
This parameter defines the low throughput threshold for the throughput measurement of the E-DCH NRT MAC-d flow. The threshold is defined as a number of bits per second. The throughput measurement measures the number of bits transmitted by E-DCH NRT MAC-d flow during the sliding measurement window. The sliding measurement window is defined with the parameter EDCHMACdFlowThroughputAveWin. If the result of the throughput measurement is less than or equal to the threshold the EDCHMACdFlowThroughputTimetoTrigger timer is started .
Parameters for E-DCH Release (II)

Parameter EDCHMACdFlowThroughputAveWin
Scope RNC Range 0.5 to 10, step 0.5 s Default 3 s
This parameter defines the size of sliding averaging window for the throughput measurement of the E-DCH NRT MAC-d flow. The throughput measurement measures the number of bits transmitted by E-DCH MAC-d flow during the sliding measurement window. Value 0 of the parameter means that E-DCH MAC-d flow throughput measurement is not performed.

RAS06 Delta Module2 Features &amp; Main Parameters

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

RAS06 Delta Module2 Features &amp; Main Parameters

Transféré par

Droits d'auteur :

Formats disponibles

RAS06 Delta Optimization

Module 2 Feature & Parameter update

Soc Classification level 1 Nokia Siemens Networks

Presentation / Author / Date

Soc Classification level 2 Nokia Siemens Networks

Presentation / Author / Date

Module 2 Feature and Parameter update

Soc Classification level 3 Nokia Siemens Networks

Presentation / Author / Date

HSUPA resource handling

Enhanced HSDPA mobility handling

Soc Classification level 4 Nokia Siemens Networks

Presentation / Author / Date

Summary of RAS06 HSPA Features

Feature Number RAN1013 RAN852 RAN853 RAN1033 RAN1034 RAN312

RAS06 Optional Optional Optional Optional Optional Basic Optional Optional

RAN1249 RAN1305 Feature Number

Optional Basic RAS06

Soc Classification level 5 Nokia Siemens Networks

Presentation / Author / Date

HSDPA Features Resource allocation

Optional enhanced functionality

HSDPA uplink associated DPCH scheduling HSDPA Channel Switching

Basic HSDPA with QPSK and 5 Codes HSDPA 16-QAM Support

HSDPA Features Mobility, multi-RABs, Number of HSDPA users

HSPA SCC over Iur, Inter Frequency HSPA Mobility

HSDPA with Additional RAB Initiation, HSDPA suspension

+ HSPA with Simultaneous AMR Voice Call

HSDPA 16 Users per Cell

+ HSPA 48 Users per Cell

HSDPA Dynamic Resource Allocation (DRA)

Dynamic Code Allocation

Soc Classification level 8 Nokia Siemens Networks

Presentation / Author / Date

Soc Classification level 9 Nokia Siemens Networks

Presentation / Author / Date

HSDPA Code Multiplexing

Presentation / Author / Date

RAS06:Shared HSDPA Scheduler/48 users per cell- flexi rel 1

Shared HSDPA Scheduler for Baseband Efficiency

Example 3: Shared HSDPA Scheduler for BB Efficiency 1*80 CE

48 users 48 users 48 users

48 Users per Cell

Up to 14.4 Mbps per cell (with code multiplexing)

Example 4: 48 Users per cell 3*80CE

RAS06:Shared HSDPA Scheduler/48 users per cell- ultra

Shared HSDPA Scheduler for Baseband Efficiency

Example 3: Shared HSDPA Scheduler for BB Efficiency 1*64 CE

48 users 48 users 48 users

48 Users per Cell

Example 4: 48 Users per cell 3*64CE =192

Example 1: 1+1+1: 2 x32 CE

16 users 16 usersTcell = 6 16 users

Presentation / Author / Date

Maximum number of HSDPA schedulers simultaneously active

Soc Classification level 14 Nokia Siemens Networks

Presentation / Author / Date

1 x SF4 2 x SF4 2 x SF4 2 x SF2 2 x SF2

1.45 Mbps 2.8 Mbps 5.74 Mbps

E-DCH serving cell is always same as HSDSCH serving cell

HSUPA HSDPA AMR

HSUPA Packet Scheduler

Soc Classification level 16 Nokia Siemens Networks

RAS06 Delta Module2 Features & Main Parameters

RAS06 Delta Module2 Features & Main Parameters