RAS06 Delta Module2 Features & Main Parameters

7/30/2019 RAS06 Delta Module2 Features & Main Parameters

1/123

1 Nokia Siemens Networks Presentation / Author / Date

Soc Classification level

RAS06 Delta OptimizationModule 2Feature & Parameter update


2/123



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

CONTENTS


3/123



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


4/123



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


5/1235 Nokia Siemens Networks Presentation / Author / Date


Summary of RAS06 HSPA Features

RAS06 features can be split to

HSDPA Telecom HSUPA Telecom

HSPA Layering

HSDPA RRM/Telecom Features Feature

Number

RAS06

16 kbit/s Return Channel DCH Data Rate Support for

HSDPA

RAN1013 Optional

HSDPA 15 Codes (requires RAN312, RAN1033 orRAN1034)

RAN852 Optional

HSDPA Code Multiplexing (requires RAN312 & RAN852)) RAN853 Optional

HSDPA 48 Users per Cell RAN1033 Optional

Shared HSDPA Scheduler for Baseband Efficiency RAN1034 Optional

HSDPA Dynamic Resource Allocation

+ Direct switch Basic

+ Dynamic HSDPA code allocation Optional

+ Dynamic DCH scheduling Optional

+ Dynamic HSDPA Power Allocation

HSDPA 10 Mbps per User RAN1249 Optional

HSDPA 14.4 Mbps per Cell RAN1305 Basic

HSUPA RRM/Telecom Features Feature

Number

RAS06

Basic HSUPA RAN826 Basic

as c as c

HSUPA BTS Packet Scheduler RAN968 Basic

HSUPA 2.0 Mbps RAN979 Optional

HSUPA Handovers RAN970 BasicHSUPA Congestion Control RAN992 Basic

HSUPA with Simultaneous AMR Voice Call RAN974 Optional

HSPA RRM/Telecom Features Feature

Number

RAS06

HSPA Layering for UEs in Common Channels RAN1011 Optional

RAN312




HSDPA Features Resource allocation

HSDPA Basic functionality Optional enhanced functionality

HSDPA resource allocationStatic code and power in RNC

HSDPA Dynamic Resource AllocationDynamic NRT DCH Scheduling

Dynamic allocation of HS-PDSCH codes

HSDPA uplink associated DPCH scheduling + 16 kbit/s Return Channel DCH Data Rate

Support for HSDPA

HSDPA Channel SwitchingPossible via cell FACH or DCH 0/0

Direct switching between DCH and HS-DSCH

Basic HSDPA with QPSK and 5 Codes + HSDPA 15 Codes & code multiplexing

HSDPA 16-QAM Support

RAS06 features




HSDPA Features Mobility, multi-RABs, Number of

HSDPA users

HSDPA Basic functionality Optional enhanced functionality

HSDPA Serving Cell Change and HSDPA

Soft/Softer Handover for Associated DPCH HSPA SCC over Iur,

Inter Frequency HSPA MobilityHSDPA Cell Reselection

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


8/123



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 Code Allocation

Dynamic allocation of HS-PDSCH codes with HSDPA 15 codes feature

RNC applies HSDPA dynamic resource allocation if Parameter

HSDPADynamicResourceAllocationis set to Enabled


9/123



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

13,286,247,049,66,723,361,6RLC payload (Mbps)

13,9446,5527,39210,087,0563,5281,68RLC bit rate (Mbps)

394460422110RLC blocks/TTI

336336336336336336RLC PDU (bits)

14,05656,58857,46810,12557,07753,6491,815Max. transport channel (MAC-d flow) bit rate (Mbps)

1317714936202511415572983630Max. transport block size (bits)

14,46,727,6814,49,64,82,4Air interface bit rate (Mbps)

78151055Number of HS-PDSCH codes

Cat 9-10Cat 9-10Cat 9-10Cat 7-8Cat 6Cat 11-12UE category

16-QAM16-QAM16-QAM16-QAM16-QAMQPSKModulation

14.4Mbps

Total

14.4 Mbps

user 2

14.4 Mbps

user 1

+ 10 Mbps+ 15 code16-QAMQPSKFeatures

13,286,247,049,66,723,361,6RLC payload (Mbps)

13,9446,5527,39210,087,0563,5281,68RLC bit rate (Mbps)

394460422110RLC blocks/TTI

336336336336336336RLC PDU (bits)

14,05656,58857,46810,12557,07753,6491,815Max. transport channel (MAC-d flow) bit rate (Mbps)

1317714936202511415572983630Max. transport block size (bits)

14,46,727,6814,49,64,82,4Air interface bit rate (Mbps)

78151055Number of HS-PDSCH codes

Cat 9-10Cat 9-10Cat 9-10Cat 7-8Cat 6Cat 11-12UE category

16-QAM16-QAM16-QAM16-QAM16-QAMQPSKModulation

14.4Mbps

Total

14.4 Mbps

user 2

14.4 Mbps

user 1

+ 10 Mbps+ 15 code16-QAMQPSKFeatures


10/123



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 increaseachievable 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

2 ms

HS-SCCHs

HS-DSCH

Demodulation information

User data

Control data

= User 1

= User 2


11/123



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

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

10 users

16 users22 users

Example 3:

Shared HSDPA

Scheduler for BB

Efficiency1*80 CE

48 users

48 users48 users

Example 4:

48 Users per cell

3*80CE

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)


12/123



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

10 users

16 users22 users

Example 3:

Shared HSDPA

Scheduler for BB

Efficiency1*64 CE

48 users

48 users48 users

Example 4:

48 Users per cell

3*64CE =192

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 schedule(=per cell)


13/123



Several 16 Users per BTS Schedulers in BTS by Tcell

grouping from RNC

16 Users per BTS Scheduler -feature requires 32 CEof processing capacity to be enabled for one to threecells in the BTS.

Another 32 CEs can be added so that cell A (blue) ishandled by first 32 CE and cells B (yellow) and C(yellow) by the second 32 CEs.

Cells are grouped to each scheduler with Tcellparameter from RNC.

Max 4 schedulers per BTS

Rules for grouping (max 4 groups):

Group 1: Tcell values 0, 1 and 2



Group 4: Tcell value 9

Example 1:

1+1+1: 2 x32 CE

f1

f2

2+2+2: 4 x32

CE

16 users

16 users

16 users

16 users

11 users

16 users5 users

B

A

Tcell = 0Tcell = 3

Tcell = 4

Tcell = 0 Tcell = 1Tcell = 2

Tcell = 3

Tcell = 6

Tcell = 9

4 schedulers (max 5 codes and 16 users):

F1: 3 cells sharing one scheduler

F2: 1 scheduler per cell


14/123



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


15/123



HSUPA

Basic HSUPA throughput can be up to

1.44 Mbps/user but it can be maximum 2.0

Mbps/user with separate feature. Thisdepends 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 connectionover HSUPA

Soft/softer Handovers are supported with

new HSPA specific FMCS parameter set

E-DCH serving cell is always same as HS-

DSCH serving cell

1 x SF4 0.71 Mbps

# of codes 10 ms

2 x SF4 1.45 Mbps

1

UE category

2

3

4

5

2 x SF4 1.45 Mbps

2 x SF2 2.0 Mbps

2 x SF2 2.0 Mbps

62 x SF2

+ 2 x SF4 2.0 Mbps

-

2 ms

-

1.45 Mbps

2.8 Mbps

-

5.74 Mbps

Max L1 data rate/user

HSUPA

HSDPA

AMR


16/123



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

Load

Prx

PrxLoadMarginEDCH

PrxMaxTargetBTS

Throughput-based Power-based

RNC PS

DCH

scheduling

domain


17/123



HSUPA Round Trip Time 52 msNSN 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 HSUPAterminal prototype

Node-B RNC Packet coreServer

Nokia Siemens networks

Approximate round trip times:

Minimum = 40ms, Maximum = 66ms, Average = 52ms


18/123



Module Contents

HSDPA resource handling

HSDPA Dynamic Resource Allocation Dynamic power allocation

Dynamic NRT DCH scheduling

Prioritisation between HSDPA and NRT DCH power resources


HSDPA code multiplexing HSDPA associated uplink DPCH scheduling




19/123



HSDPA power allocation methods

HSDPADynamicResource-Allocation

RNC sends the

PtxMaxHSDPA

to BTS

BTS allocates the

available DL power

dynamically to

HSDPA until PtxMaxHSDPA

DisabledBTS allocates the

available DL power dynamically

to

HSDPA until PtxCellMax/MaxDLPowerCapability

DL power

Enabled

RNC schedules NRT DCH

according to HSDPApriority

RNC schedules NRT DCH

using dynamic NRT

scheduling

HSDPA (Static)

Resource Allocation

HSDPA dynamic

Resource Allocation

Min(PtxMaxHSDPA,min(PtxCellMax,MaxDLPowerCapability

)-PtxTargetHSDPA)


20/123



HSPA Power

BTS periodically reports the total transmission power value PtxTotal and non-HSDPApower

Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCHtransmission if BTS supports only HSDPA

or

non-HSPA power (Transmitted carrier power of all codes not used for HS-PDSCHHS-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 thecell maximum transmission power, defined by MIN[PtxCellMax, MaxDLPowerCapability]

From the difference of reported PtxTotal and HSxPA power, RNC can calculate the usedHSPA-power value and update that to statistics counters

The counters are updated only when there is at least one HSDPA allocation in thecell

RNC updates the HSxPA power value counters when nbap_radio_resource_ind_smessage including PtxTotal and HSxPA power information is received from BTS andthere is at least one HSDPA allocation in the cell

The unit for all counter updates is watt


21/123



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. PtxTargetremains 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 settingsPtxMax

PtxNC

PtxNRT

PtxHSDPA

PtxNonHSPA

PtxHighHSDPAPwr

PtxTargetPSMax

PtxTargetPSMin

HSDPA active

PtxTarget +PtxOffset

PtxTargetPS

PtxTotal

PtxTargetPSTarget


22/123



Module Contents


HSDPA Dynamic Resource Allocation Dynamic power allocation


Prioritisation between HSDPA and NRT DCH power resources


HSDPA code multiplexing HSDPA associated uplink DPCH scheduling




23/123




RNC affects the HSDPA power allocation indirectly by scheduling NRT DCH bitrates

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 (thiswas PtxTargetHSDPA for R99 in RAS5.1)

PtxTargetPS is adjusted between PtxTargetPSMin and PtxTargetPSMax

PtxTargetPSAdjustPerioddefines the adjustment period for the PtxTargetPS interms of Radio Resource Indication (RRI) reporting periods

IfPtxTargetPSMaxand PtxTargetPSMin are set to the same value, RNC doesnot adjust PtxTargetPS Dynamic NRT DCH scheduling disabled

PtxTargetPSMin

PtxTargetPS PtxTargetPSMax


24/123




With no active HSDPA users:

1) NRT DCH scheduling to the

PtxTarget+PtxOffset&RT DCH admission

to PtxTarget

With active HSDPA users:

2) NRT DCH scheduling to PtxTargetPS

3) RT DCH admission to PtxTarget

HSDPA activeNo HSDPA users No HSDPA users

PtxTarget

+PtxOffset

PtxMax

PtxTargetPS

PtxNC

PtxNRT

PtxHSDPA

1

2

3

PtxNonHSPA

PtxTotal


25/123



Dynamic NRT DCH scheduling Adjustment

Initial value of the PtxTargetPS is the lower from the following ones: PtxTargetor

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

PtxTargetremains 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, HS-

SCCH, 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 thePtxTargetPSStepUp and PtxTargetPSStepDown management parameters


26/123



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

PtxHighHSDPAPwris 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


27/123



MAC-d flow(s) setup in the cell

NRT DCH user(s) in the cell

PtxTotal received

Yes

PtxTotal >=PtxHighHSDPAPwr

NoPtxTargetPS >

PtxTargetPSTarget

Yes

No decrease

Check increase

No

Decrease PtxTargetPS

Dynamic NRT DCH scheduling PtxTargetPS decrease

PtxTargetPS is decreased if

PtxTotal > PtxHighHSDPAPwr

= HSDPA power congestion

& PtxTargetPS > PtxTargetPSTarget

Above target value

Amount of decrease is determined

by the management parameter

PtxTargetPSStepDown, but limited

to

PtxTargetPS PtxTargetPSTarget

PtxTargetPSTarget = target (ideal)value of the NRT DCH

scheduling target

D i NRT DCH h d li Pt T tPS i


28/123



Dynamic NRT DCH scheduling PtxTargetPS increase

PtxTargetPS is increased if

PtxNonHSPA > PtxTargetPS - 1 dB

= Power congestion on DCH

& PtxTargetPS < PtxTargetPSTarget

Below target value

Amount of increase is determined by

the management parameterPtxTargetPSStepUp

PtxTargetPSTarget = target (ideal)value of the NRT DCH

scheduling target

MAC-d flow(s) setup in the cell

NRT DCH user(s) in the cell

PtxNonHSPA received

Yes

PtxNonHSPA >=

(PtxTargetPS - 1 dB)

Yes

No increaseCheck decrease

No

Increase PtxTargetPS

NoPtxTargetPS CodeMIN

Available SF128 codes


48/123



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


49/123



Periodical HS-DSCH codedowngrade if the number of

currently available SF128codes is lower thanHSPDSCHMarginSF128(default 8)

HS-DSCH code downgrade

due to NRT DCH codecongestion is allowed ifnumber of currently allocatedHS-PDSCH codes is greaterthan Maximum code set-DPCHOverHSPDSCHThresh

old (default 0, no downgradepossible due to NRTcongestion !!!)

Numbero

fallocatedSF16codes

NumberofreservedS

F128codes

DPCHOverHSPDSCHThreshold

6

78

9

10

11

12

1314

15 Maximum in

code set

HSPDSCHMarginSF128

5

38

48

58

68

78

88

98

108118

128

0

Code tree optimisation


50/123



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 parameterCodeTreeOptimisation 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


51/123



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


52/123

Example:Number of codes vs. PPP Throughput


53/123



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

2

4

6

8

10

12

14

034

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

986

time / sec

PPPthroughput/bps

-140.0

-120.0

-100.0

-80.0

-60.0

-40.0

-20.0

0.0

avg. Codes

RSCP

Example: Used modulation 5 codes vs. 10 codesRSCP drops


54/123



With 10 codes the modulation

is switched 16-QAM QPSK

prior to decreasing number ofcodes (you can see 5 or 10

codes in the picture but

change of modulation)

HSDPA modulation - 10 codes

0%

20%

40%

60%

80%

100%

0 50 100 150 200 250 300 350 400 450 500 550 600 650 700 750 800 850 900 950

s

QPSK 16-QAM NA

HSDPA modulation - 5 codes

0%

20%

40%

60%

80%

100%

0 50 100 150 200 250 300 350 400 450 500 550 600 650 700 750 800 850 900 950

s

QPSK 16-QAM NA

RSCP drops


55/123

Example: DL throughput 5 codes


56/123



Large variation on DL bit rate due to fading

Some packet drops also cause bit rate drop

DL PPP throughput

0

500000

1000000

1500000

2000000

2500000

3000000

3500000

4000000

4500000

5000000

035

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

980

time / sec

PPPthroughput/bps

-140.0

-120.0

-100.0

-80.0

-60.0

-40.0

-20.0

0.0

PPP DL

RSCP

Module Contents


57/123



RAS06 main features





HSUPA resource Handling


HSDPA Code Multiplexing


58/123



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


59/123



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


60/123



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-HSscheduler in BTS

HSDPA 48 Users per Cell is activated with the RNC level RNP parameterHSDPA48UsersEnabled

Sensible Iub and BTS baseband dimensioning requires that also feature 16 kbit/sReturn Channel DCH Data Rate Support for HSDPA is in use + corresponding

other HSDPA bitrate parameters

Parameters


61/123



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


62/123



RNC Parameters

Example-Test cases


63/123



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


64/123



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

2460 2442

993

5896

3669 3521

1135

8325

4340 4363

8704

0

1000

2000

3000

4000

5000

6000

7000

8000

9000

10000

Cat 8 - 1 Cat 8 - 2 Cat 6 Cell

UE type, Cell

kbit/s

No mux

Code Mux 3-HS-SCCH

Code Mux 2-HS-SCCH

Example-Max cell throughput with code mux


65/123



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

14155.0 13904.0

6898.3

10264.59585.2

6446.1

9616.7

10873.6

0.00.0

2000.0

4000.0

6000.0

8000.0

10000.0

12000.0

14000.0

16000.0

Cat 8 - 1 Cat 8 - 2 Cat 6

UE type

No mux

Code Mux 3-HS-SCCH

Code Mux 2-HS-SCCH

Scheduling example 3 HS-SCCH codes


66/123



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.

CQI

Modulation No of

PDSCH

codes

Final

TBS

PDSCH

power

(dBm)

8 36866 23 25 16QAM 7 10821 38.9688 36865 23 24 16QAM 6 8574 38.968

- - - - - - - -

6 36867 23 27 16QAM 5 7168 38.964

8 36865 23 24 16QAM 8 10629 38.964

- - - - - - - -

8 36866 23 25 16QAM 7 10821 38.978 36865 22 24 16QAM 6 8574 38.97

- - - - - - - -

Module Contents


67/123



RAS06 main features







HSDPA associated uplink DPCH channel


68/123



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 parameterHSDPA16KBPSReturnChannel

Minimum allowed bit rate with HSDPAminAllowedBitrateUL parameter

Not limited by BitRateSetPSNRT

PS: HS-DSCH (DL)

PS: DCH (UL)

PS: HS-DSCH (DL)

PS: DCH (UL)



69/123



If the HS-DSCH allocation is triggered by uplink, normal NRT DCH schedulingrules are applied

If the traffic volume measurement indicates High traffic volume, the RNC attempts toallocate a return channel with the highest possible bit rate

TrafVolThresholdULHigh parameter

If the traffic volume measurement indicates Low traffic volume, the RNC attempts toallocate a return channel with configured initial bit rate

HSDPAinitialBitrateUL parameter

If the HS-DSCH allocation is triggered by downlink, the RNC attempts to allocatethe uplink with the HSDPAinitialBitrateUL parameter

In the case of direct DCH to HS-DSCH switch, the HSDPA UL DCH bit rate canbe same as existing DCH UL bit rate

If even initial bit rate or higher can not be allocated, HS-DSCH allocation is notpossible

DL/UL DCH is scheduled to the UE



70/123



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 bitrate 64 kbps


71/123



The initial bit rate (HSDPAinitialBitrateUL) is set to 64 kbps. The minimum bit rate

is set to 16 kbps (HSDPAminAllowedBitrateUL)

64

kbps

384

128

t

0

Capacity

Request

(Traf.vol

measurement

low)

Initial bitrate

64 kbps

Decrease of the

retried NRT DCH

bitrate

Priority based

scheduling/

RT-over-NRT

Minimum bitrate

16 kbps

Capacity

Request

(Traf.vol

measurement

high)

Capacity

Request

(Traf.vol

measurement

high)

t1

t2

t3

t5

16

t4

Example use case 2: Initial bit rate 128 kbps


72/123



Example- DL performance with 16 kbits/s returnchannel


73/123



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

0

200000

400000

600000

800000

1000000

1200000

020

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

740

time

PPPthroughput/bps

Parameters



74/123




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 bitrate 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 (512bytes), 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. 24KB), 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


75/123



Module Contents

RAS06 main features Basic Signalling


76/123



RAS06 main features


HSUPA resource Handling HSUPA Overview

HSUPA Packet Scheduling

HSUPA Mobility

HSUPA Release


Basic Signalling

Ue Capability

Transport Block size Happy Bit

HSUPA - General principle


77/123



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

Cell in active set

HSUPA UE

E-DPDCH + E-DPCCH (scheduling request)

Node B completes scheduling based on happy bit and cellload

Node B grants the E-DPDCH transmit power ratio eachUE is allowed to use

UE selects the highest bit rate that it is allowed accordingthe granted power and the allowed Transport FormatCombination Set (TFCS)

UE is allowed to use the scheduled bit rate until receiving

the next grantSHO is supported.Non serving cell can only send

down/hold power commands.

E-DCH Transport Block Sizes RAS06 supports 10 ms TTI and Transport Block (TB)

size table 1


78/123



This table is optimised by 3GPP for RLC PDU sizes of

336 and 656 bits

The UE must select an appropriate TB size from thistable 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


79/123

Happy Bit

Happy Bit forms input for MAC-e scheduler


80/123



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

HappyBitDelayConditionEDCH RNC

Parameter Scope Range Default 50 ms

This parameter determines the value for the Happy Bit Delay Condition. This information element is signalled to the UE usingthe RRC protocol. The UE uses this parameter to help set the happy bit.

2, 10, 20, 50, 100, 200,

500, 1000 ms

Always equal to 1 for 10 ms TTI

Module Contents

RAS06 main features


81/123



RAS06 main features



HSUPA Overview


HSUPA Mobility

HSUPA Release


HSUPA Requirements & Parameters

Feature requirements:


82/123



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 handoverand HSUPA BTS packet scheduler become automatically available

Parameter requirements:

Definition of HSPA FMCS_id if ADJS are present for the WCEL (same of FMCx ofHSDPA 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 node-B: 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


83/123



The EDCHQOSClassesparameter can be used to select which traffic classes

are able to use HSUPA.

This parameter must be configured to be consistent with the equivalent HSDPAparameter (HSDSCHQoSclasses).

Max number of HSUPA connections

per cell (MaxNum berEDCHCell, max 20)

per logical cell group (MaxNumb erEDCHLCG, max 24).

It is also possible to reserve a subset of the total number of connections forHSUPA soft handover (NumberEDCHReservedSHOBranchAddit ions)

The MaxTotalUpl inkSymbolRate(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


84/123



RNC scheduler continues to manage R99 DCH connections

Similar to HSDPA scheduler in MAC-hs, HSUPA scheduler in MAC-e is fasterthan an RNC scheduler

HSUPA throughput is controlled with absolute and relative grants

Scheduling period is 10 ms

Zero Grant

8

16

32

64

128

384

256

Zero Grant

8

16

32

64

128

384

256

Zero Grant

8

16

32

64

128

384

256

1. RNC limits the E-TFCI based upon UEcapability and QoS profile

2. Node B limits E-TFCI based upon packet

scheduling principles

3. UE limits E-TFCI based upon transmit power

capability

4. UE selects E-TFCI based upon data to be

transferred

1.

RNC Node B

2.

UE

3.

4.


HSUPA scheduler combines throughput and load based algorithms

Throughput based scheduling is applied for lower loads


85/123



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)

Iub capacity

Available baseband processing capacity

Prx

PrxLoadMarginEDCH

PrxMaxTargetBTS

Throughput-based Power-basedRNC PS

DCH

scheduling

domain

Minimum Throughput for E-DCH scheduling in BTS

BTS does not do any power estimations and interference threshold checkings


86/123



y p g

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.


87/123



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 PrxTargetHSUPA activeNo HSUPA users No HSUPA users

PrxTargetPSMin

PrxTarget

PrxNC

PrxNRT

PrxEDCHPrxTargetPSMax

Prx_Target_PS

PrxMaxTargetBTS Prx_Target_PS is applicableto NRT scheduling and can be

adjusted betweenPrxTargetPSMax and

PrxTargetPSMin

RNC sends PrxMaxTargetBTS and Lmincell to the Node B

Node B Scheduling Procedure (Initial Conditions)


88/123



-105

-104

-103

-102

-101

-100

-99

-98

-97

-96

-95

0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1

Load

RTWP(dBm) PrxMaxTargetBTS (from

RNC)

Node B calculates the maximum target load from PrxTarget BTS

Lmincell (from

RNC)

Max Cell Load

(Calculated from PrxMaxTargetBTS)

Throughput based Power

based

Own Cell Load

Node B calculates the own cell load

Node B Scheduling Procedure (Throughput Based)


89/123



-105

-104

-103

-102

-101

-100

-99

-98

-97

-96

-95

0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1

Load


RNC)

Lmincell (from

RNC)

Max Cell Load

(Calculated from PrxMaxTarget)

Own Cell Load

If calculated own cell load is less than Lmincell then throughputbased

scheduling can be applied to increase the own cell load to Lmincell

Calculated Own

Cell Load

Schedule

Resource

If calculated own cell load is greater than Lmincell thenpower based

scheduling is applied to increase the total cell load to Max Cell Load

Node B Scheduling Procedure (Power Based I)


90/123



-105

-104

-103

-102

-101

-100

-99

-98

-97

-96

-95

0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1

Load


RNC)

Lmincell (from

RNC)

Max Cell Load


Own Cell Load

scheduling is applied to increase the total cell load to Max Cell Load

Calculated Own

Cell Load

Node B measures actual RTWP and calculates the actual load

Node B Scheduling Procedure (Power Based II)


91/123



-105

-104

-103

-102

-101

-100

-99

-98

-97

-96

-95

0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1

Load


RNC)

Lmincell (from

RNC)

Max Cell Load


Own Cell Load

Calculated Own

Cell Load

Measured RTWP

(Received Total

Wideband Power)Schedule

Resource

Calculated Total

Cell Load

Parameters for Node B Scheduling (I)

PrxMaxTargetBTS WCEL

Parameter Scope Range Default 6 dB

0 to 30, step 0.1 dB


92/123



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 + PrxOffsetbecause the Node B is more responsive than the RNC

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 receiveduplink power to system noise

Parameters for Node B Scheduling (II)

Parameter Scope Range Default -101.9 dBm

130 t 50 t


93/123



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

PrxNoise WCEL

Defines the noise level in the BTS digital receiver when there is no load (thermal noise + noise figure). This parameter isrequired for noise rise calculations.

-130 to -50, step

0.1 dBm

Parameters for Node B Scheduling (III)

PrxLoadMarginEDCH WCEL

Parameter Scope Range Default 2 dB

0 to 30 step


94/123



inEDCHxLoadMP

PL

noiserx

noiserx

minCELLargPr

1_

_

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:

PrxLoadMarginEDCH WCEL 0 to 30, step0.1 dB

Defines the own cell uplink load (DCH and E-DCH) threshold used to trigger the use of power based scheduling. Throughputbased scheduling is used when the own cell load is below this threshold.

Private NBAP message is used to transfer LminCELL to the Node B

Downlink Physical Channels-Transmit PowerParameters


95/123



PtxOffsetEHICH WCEL -32 to 31.75, step 0.25 dB

Parameter Scope Range Default -11 dB

Transmission power of the E-HICH. E-HICH power is relative to the transmission power of primary CPICH.

PtxOffsetERGCH WCEL -32 to 31.75, step 0.25 dB


Transmission power of the E-RGCH. E-RGCH power is relative to the transmission power of primary CPICH.

PtxOffsetEAGCH WCEL -32 to 31.75, step 0.25 dB


Transmission power of the E-AGCH. E-AGCH 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


96/123



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

The E-AGCH can rapidly increase the bit rate allocated to a UE

Fast Ramp-Up of Bit Rate


97/123



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

Tup Default 50 ms

The period during which a UE grant is

not allowed to increase

Non-Configurable

Scheduling Procedure (I) The scheduling procedure is

completed every 10 ms

Handling non-serving cell overload


98/123



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

TargetNSEDCHToTotalEDCHPR WCEL

Parameter Scope Range Default 50 %

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.

0 to 100, step 1 %

E-RGCH used to send the down command

Scheduling Procedure Handling non-serving cell overload

Handling congestion indicators

The load of the serving and non serving cell

should not be too high

Iub congestion should not be too high (Delay


99/123



Handling Low Utilisation UE

Lrx_EDCH_Allowed =

Max(Lrx_EDCH_Power, Lrx_EDCH_Throughput)

Lrx_EDCH_Allowed > 0

Load increase

estimation

Allocate Grant

Load decrease

estimation

Allocate Grant

Calculate the maximum of the loadincreases 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

Yes No

Iub congestion should not be too high ( Delay

Build-up or Frame Loss)

Ue uses lower grant than allocated by

Node B

Load Increase Estimation

Single Modifiable unhappy UE?Yes


100/123



g ppy

Fast Ramp-UpProcedure

Increase the bit rate of the

modifiable unhappy UE using theE-RGCH

Load increaseestimation

Modifiable unhappy UE Exists?

Sufficient margin to allow an

increaseHardware resources available?

Yes

No

Yes

Yes

No

Exit

No No

Load Decrease Estimation


101/123



Load remains above Target?

Decrease the UE bit rate using

the E-RGCH

Active E-DCH Exists?

Yes

Yes

No

Exit

Load decrease

estimation

No

Exit

Other Scheduling Mechanisms

All of the following mechanisms use the E-AGCH

f f


102/123



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


103/123

Examples-HSUPA data rate Limitation

Limitation of HSUPA data rate

100%

Power Grant Data

This picture shows what was thelimiting factor of the throughputduring the data transfer.


104/123



0%

20%

40%

60%

80%

100%

0 50 100 150 200 250 300 350 400 450 500 550 600 650 700 750 800 850 900 950

s

Grant 92% of time

Data 6% of time UL Power 1% o time

Data means that Ue hadempty buffer no new data tosend

At low RSCP more samples withUL Power limitation

But also a bit more Datalimitation, most likely iscaused by the UL powerlimitation caused TCP/IPcongestion control to kick in

Examples-Average HSUPA TB Size

average HSUPA TB size The TB size was


105/123



average HSUPA TB size

0

5000

10000

15000

20000

25000

0 50 100 150 200 250 300 350 400 450 500 550 600 650 700 750 800 850 900 950s

bit

The TB size wasmost of the time20000

Some variationclearly visible duringthe lower RSCP.

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


106/123


Soc Classification level-40

-30

-20

-10

0

10

20

30

-85 -80 -75 -70 -65 -60 -55 -50 -45 -4

RSCP [dBm]

SGRANT UETXP AGRANT as SG Measured MACe tput [mbps]*10

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

At high RSCP the absolute grantis seldom used and therefore also

the throughput is having less

fluctuation compared to low

RSCP

10 140

Happy bit Grant Type Allocated E-TFCI

HSUPA Throughput Test Analysis Downgrades andUpgrades

Grant Type:

3 = Downgrade by RGCH

2 = Upgrade by RGCH


107/123



0

1

2

3

4

5

6

7

8

9

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

SFN

HappyBit&

GrantType

0

20

40

60

80

100

120

E-TFCI

pg y

1 = Upgrade/Downgrade by AGCH

Module Contents

RAS06 main features



108/123



g



HSUPA Mobility

HSUPA Release

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


109/123



NumberEDCHReservedSHOBranchAdditions

Inter-frequency and inter-system mobility is provided via DCH in the sameway 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 bestcell 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


110/123



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 CellChange

Event Description Actions on HSDPA

1A A primary CPICH enters the reporting

range.Start HSDPA specific measurements


111/123



g

1B A primary CPICH (Serving HS-DSCH cell)leaves the reporting range. Trigger for serving HS-DSCH cell change

1C A non-active primary CPICH becomes

better than an active (Serving HS-DSCH

cell) one

Trigger for serving HS-DSCH cell change

6F/6G UE Rx-Tx time difference for a RL

included in the active set becomes larger

than an absolute threshold

Trigger for serving HS-DSCH cell change

1F A primary CPICH goes below the absolute

threshold.Trigger for releasing the HS-DSCH MAC-d flow (after 1F for

all AS cells) + for AMR multi-RAB inter-frequency/-RAT

measurements

6A UE Tx power exceeds the absolute

threshold.Trigger for releasing the HS-DSCH MAC-d flow + for AMR

multi-RAB inter-frequency/-RAT measurements

Uplink quality deterioration report (in RNC) Trigger for releasing the HS-DSCH MAC-d flow

DL transmitted code power > limit Trigger for releasing the HS-DSCH MAC-d flow + for AMRmulti-RAB inter-frequency/-RAT measurements

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


112/123



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

E-DCH area

Non-E-DCH

area

Non-E-DCH

area

HSUPA mobilityquality 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


113/123



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 HSUPAserving cell (default 2 dB)

EDCHCTSwitchGuardTimer

parameter defines a time

window during which channel

type switching from DCH to E-

DCH is disallowed after aswitch from E-DCH to DCH

(default 2s)

HSUPA mobilityquality triggers

If the initial channel allocation (initial channel type selection between DCH and E-

DCH), 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


114/123



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.

EDCHAddEcNoOffsetparameter

defines a window below the CPICH

Ec/Io of the HSDPA serving cell

(default 0 dB)

Parameter sets in soft handover

The WCEL:HSPAFmcsident i f ieris used when a single NRT PS RAB is

establsihed having HS_DSCH and E-DCH transport channel allocated


115/123



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: RTWithHSPAFmcsIdent i f ieris used when AMR speech CS RAB is

established simultaneously with an NRT PS RAB having HS-DSCH and E-DCH

transport channel allocated.

HSUPA Throughput during SCC- example

edtoactiveset

pedfroma

ctiveset


116/123



Throughput vs. time

0

500000

1000000

1500000

2000000

2500000

7:56:43

7:56:43

7:56:44

7:56:44

7:56:45

7:56:45

7:56:46

7:56:47

7:56:47

7:56:48

7:56:48

7:56:49

7:56:49

7:56:50

7:56:51

7:56:51

7:56:52

7:56:52

7:56:53

7:56:53

7:56:54

7:56:54

7:56:55

Time

Tput(Mbps)

MACTPUTUL

GRANTEDTPUT

2ndc

ella

dde

1st celld

rop

Gap ~600ms

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 oneHHO relocation triggeredRelocation triggered


117/123



2,5Mbit/s

second on a 64/64, actual user plane

break in this case ~4.5 s

HSPA to DCH switchDCH to HSPA switch

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

Implementation at RAS06 E4:

HSPA service is switched to DCH at the RNC

border area

Module Contents

RAS06 main features



118/123





HSUPA Mobility

HSUPA Release

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

f f


119/123



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


120/123



TTI

EDCHMACdFlowThroughputAveWin

ThroughputResult

EDCHMACdFlowThroughputTimetoTrigger

Low throughput indication

sent to layer 3

Normal throughput indication

sent to layer 3

EDCHMACdFlowThroughputRelThr

Low throughput indication is sent if timer reaches

EDCHMACdFlowThroughputTimetoTrigger

IfEDCHMACdFlowThroughputTimetoTrigger = 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

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:


121/123



HS-DSCH MAC-d flow has low utilization and E-DCH can be released as a resultof low throughput

Or

HS-DSCH MAC-d flow has low throughput and E-DCH can be released. In this

case UE specific timerHsdschGuardTimerLowThroughputis started

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)


122/123

Parameters for E-DCH Release (II)

EDCHMACdFlowThroughputAveWin RNC 0.5 to 10, step 0.5 s

Parameter Scope

Range Default 3 s


123/123



This parameter defines the size of sliding averaging window for the throughput measurement of the E-DCH NRT MAC-dflow. 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 & Main Parameters

Documents

Transcript of RAS06 Delta Module2 Features & Main Parameters