09_RN31639EN40GLA0_RANPAR1_HSDPA_RRM_v1.1_RU40

1 Nokia Siemens Networks RN31639EN40GLA0

HSDPA basics & RRM


HSDPA RRM & parameters: Module Objectives

At the end of the module you will be able to:

Explain the physical layer basics of HSDPA technology

List the capabilities & enhancements of HSDPA

Explain the principles of HSDPA RRM


HSDPA RRM: Contents

HSDPA Principles

HSDPA Physical Channels

RU40 Capabilities & Baseband Configuration

HSDPA Packet Scheduling

Basics of HSDPA Power Allocation

Basics of HSDPA Code Allocation

Basics of HSDPA Mobility

HSDPA Channel Type Selection

Associated UL DCH

Appendix


HSDPA Principles

High Speed Downlink Packet Access (HSDPA) based on:

Node B decisions

Multi-code operation

Fast Link Adaptation Adaptive Modulation & Coding AMC

Fast Packet Scheduling

Fast H-ARQ

Fast 2 ms TTI*

Downwards Compatibility with R99 (shared or dedicated carrier)

* TTI = 1 Subframe = 3 Slots = 2 ms

H-ARQ: Hybrid Automatic Repeat Request

Motivation:

- enhanced spectrum efficiency

- higher peak rates >> 2 Mbps

- higher cell throughput

- reduced delay for ACK transmission

3GPP Rel. 5; TS 25.308:

HSDPA Overall Description

HSDPAenabled WCEL; 0 = disabled; 1 = enabled


Adaptive Modulation & Coding (1/2)

I

Q 0000

0010

0011

0001

1000

1010

1011

1001

1100

1110

1111

1101

0100

0110

0111

0101

16QAM

4-Bit Keying QPSK

2-Bit Keying

Q

I

(1,1) (0,1)

(1,0) (0,0)

HSDPA uses

QPSK 16QAM 64QAM* dynamically based on

quality of the radio link

* defined in 3GPP Rel. 7 / implemented with NSN RU20


Adaptive Modulation & Coding (2/2)

Rate

Matching

Puncturing /

Repetition

Turbo Coding

1/3

Effective

Code Rate:

1/4 - 3/4

HSDPA Adaptive Coding

based on the R99 1/3 Turbo Coding

Rate Matching: Puncturing or Repetition

code rate: 1/6 4/4

dynamically based on quality of the radio link


C1,0 = [1]

C2,1 = [1-1]

C2,0 = [11]

C4,0 = [1111]

C4,1 = [11-1-1]

C4,2 = [1-11-1]

C4,3 = [1-1-11]

C8,0 = [11111111]

C8,1 = [1111-1-1-1-1]

C8,2 = [11-1-111-1-1]

C8,3 = [11-1-1-1-111]

C8,4 = [1-11-11-11-1]

C8,5 = [1-11-1-11-11]

C8,6 = [1-1-111-1-11]

C8,7 = [1-1-11-111-1]

C16,0 = [.........]

C16,1 = [.........]

C16,15 = [........]

C16,14 = [........]

C16,13 = [........]

C16,12 = [........]

C16,11 = [........]

C16,10 = [........]

C16,9 = [.........]

C16,8 = [.........]

C16,7= [.........]

C16,6 = [.........]

C16,5 = [.........]

C16,4 = [.........]

C16,3 = [.........]

C16,2 = [.........]

SF = 1 2 4 8 SF = 16 256 512 ...

SF = 16

240 ksymb/s

Multi-Code operation:

1..15 codes

0.24 .. 3.6 Msymb/s

Multi Code Operation (1/3)


Multi Code Operation (2/3)

RU20 includes

3GPP Rel. 7 features:

64QAM (RAN1643)

Modulation

QPSK

Coding rate

1/4

2/4

3/4

5 codes 10 codes 15 codes

600 kbps 1.2 Mbps 1.8 Mbps

1.2 Mbps 2.4 Mbps 3.6 Mbps


16QAM

2/4

3/4

4/4




64QAM

3/4

5/6

4/4




64QAM

6 bits/symbol

HSDPA64QAMAllowed

WCEL; 0 (Disabled), 1 (Enabled)


Multi Code Operation (3/3): HSDPA UE capability classes

HS- DSCH

category

max. No.

of

HS-DSCH

Codes

min. *

Inter-

TTI

interval

Modulation

Dual-

Stream

MIMO

supported

Peak

Rate

1 5 3 (6 ms) QPSK/16QAM No 1.2 Mbps

2 5 3 QPSK/16QAM No 1.2 Mbps





7 10 1 QPSK/16QAM No 7 Mbps




11 5 2 QPSK only No 1 Mbps

12 5 1 QPSK only No 1.8 Mbps

13 15 1 QPSK/16QAM/ 64QAM

No 17.4 Mbps

14 15 1 QPSK/16QAM/ 64QAM

No 21.1 Mbps

15 15 1 QPSK/16QAM Yes 23.4 Mbps

16 15 1 QPSK/16QAM Yes 28 Mbps

17 15 1 QPSK/16QAM/ 64QAM or Dual-Stream MIMO

17.4 or 23.4 Mbps

18 15 1 QPSK/16QAM/ 64QAM or Dual-Stream MIMO

21.1 or 28 Mbps

* TTI: Transmission Time Interval

RU20/30 include

3GPP Rel. 7/8 features:

64QAM (cat 13, 14, 17, 18)

2x2 MIMO (Dual-Stream MIMO) (cat 15, 16, 17, 18)

MIMO w/- 64QAM (cat 19, 20)

DC-HSDPA (cat 21, 22)

DCHSDPA w/- 64QAM (cat 23, 24)

RU40 include 3GPP Rel.9 features:

DCHSDPA w/-MIMO w/o 64QAM (cat 25, 26)

DCHSDPA & MIMO & 64QAM (cat 27, 28)

MIMOEnabled WCEL; 0 (Disabled), 1 (Enabled)

HSDPA64QAMAllowed


Further on HS-DSCH categories & other

parameters HSPA+ RRM


UE Iub

Uu

Red

uc

ed

retra

ns

mis

sio

n

RNC: functionalities

shifted to

Node B

more intelligence new functionalities

new UEs

HSDPA Capability

Classes

Network Modifications for HSDPA

UTRAN & UE:

modified PHY layer

modified MAC

modified transport and physical channels

modified coding

modified modulation

new Node B functionalities:

Acknowledged transmission: Fast H-ARQ faster retransmission / reduced delays ! less Iub retransmission traffic !

higher spectrum efficiency !

Fast Packet Scheduling fast & efficient resource allocation !

Fast Link Adaptation Adaptive Modulation & Coding ! compensation of fast fading (without fast PC)

higher peak rates & spectrum efficiency !

Node B


HSDPA RRM

HSDPA Principles








Associated UL DCH

Appendix


Physical Channel Overview

HS-PDSCH High-Speed Physical DL Shared Channel

HS-SCCH High Speed Shared Control Channel

associated DCH Dedicated Channel (Rel. 99)

HS-DPCCH High Speed Dedicated Physical Control Channel

Node B

MAC-hs

F-DPCH Fractional Dedicated Physical Channel (Rel. 6/7)


HS-PDSCH

HS-PDSCH: High-Speed Physical Downlink Shared Channel Transfer of actual HSDPA data

5 - 15 code channels

QPSK or 16QAM modulation

Divided into 2 ms TTIs

Fixed SF16

HSPDSCHCodeSet HS-PDSCH code set; WCEL; (-) (-) (5 codes)

Examples

00000 00000 100000 = always 5 codes reserved (default)

11010 10100 100000 = number of reserved codes adjustable (5, 8, 10, 12, 14 or 15 codes, recommended)

0-4 codes always disabled 11-15

codes

6-10

codes

HS-PDSCH code set parameter Specifies whether number of

codes channels reserved for HSDPA is fixed* or dynamically adjustable

Minimum 5 code channels / Maximum 15 codes channels

Possible numbers of code channels enabled / disabled bit wise


HS-SCCH

HS-SCCH: High-Speed Shared Control Channel L1 Control Data for UE; informs the UE how to decode the next HS-PDSCH frame

e.g. UE Identity, Channelization Code Set, Modulation Scheme, TBS, H-ARQ process information

Fixed SF128 transmitted 2 slots in advance to HS-PDSCHs NSN implementation with slow power control: shares DL power with the HS-PDSCH more than 1 HS-SCCH required when code multiplexing is used

TBS: Transport Block Size

Code multiplexing HSDPA service for several users

simultaneously

For each user individual HS-SCCH required

available only, if > 5 codes can be reserved for HS-PDSCH

SF16

HS-PDSCH

Time

User 1 User 2 User 3 User 4

Subframe

2 ms

5

10

15

MaxNbrOfHSSCCHCodes

Maximum number of HS-SCCH codes

WCEL; RU10 & earlier: 1..3; 1; 1; RU20: 1..4


HS-DPCCH

UL HS-DPCCH: High-Speed Dedicated Physical Control Channel MAC-hs Ack/Nack information (send when data received)

Channel Quality Information (CQI reports send every 4ms, hardcoded period)

Fixed SF 256

HARQ-ACK

(10 bit)

1 Slot = 2560 chip 2 Slots = 5120 chip

Subframe # 0 Subframe # i Subframe # N

1 HS-DPCCH Subframe = 2ms

CQI (20 bit)

Channel Quality Indication

TS 25.214: CQI values = 0 (N/A), 1 .. 30; steps: 1;

1 indicating lowest, 30 highest air interface quality


HS-DPCCH & CQI

P-CPICH

UE observes

P-CPICH (Ec/Io)

CQI*

1 137 1 QPSK 0

2 173 1 QPSK 0

3 233 1 QPSK 0

4 317 1 QPSK 0

5 377 1 QPSK 0

6 461 1 QPSK 0

7 650 2 QPSK 0

8 792 2 QPSK 0

9 931 2 QPSK 0

10 1262 3 QPSK 0

11 1483 3 QPSK 0

12 1742 3 QPSK 0

13 2279 4 QPSK 0

14 2583 4 QPSK 0

15 3319 5 QPSK 0

16 3565 5 16-QAM 0

17 4189 5 16-QAM 0

18 4664 5 16-QAM 0

19 5287 5 16-QAM 0

20 5887 5 16-QAM 0

21 6554 5 16-QAM 0

22 7168 5 16-QAM 0

23 9719 7 16-QAM 0

24 11418 8 16-QAM 0

25 14411 10 16-QAM 0

26 14411 10 16-QAM -1

27 14411 10 16-QAM -2

28 14411 10 16-QAM -3

29 14411 10 16-QAM -4

30 14411 10 16-QAM -5

* UE internal (proprietary) process

TB Size [bit]

CQI value 0: N/A (Out of range)

= Reference Power Adjustment (Power Offset) [dB]

CQI used for:

Link Adaptation decision

Packet Scheduling decision

ACK/NACK used for:

H-ARQ process Link Adaptation decision

HS-SCCH power adaptation

CQI TB Size # codes Modulation

CQI Table (Example) TS 25.214: Annex Table 7b

Cat 8 UE


Associated DCH (DL & UL)

DL DPCH: Associated Dedicated Physical Channel L3 signalling messages

Speech - AMR

Power control commands for associated UL DPCH

UL DPCH: (DPDCH & DPCCH) L3 signalling messages

Transfer of UL data 16 / 64 / 128 / 384 kbps, e.g. TCP acknowledgements

Speech - AMR

DPDCH / DPCCH (time multiplexed)

DPDCH: L3 signalling; AMR

DPCCH: TPC for UL DPCH power control

DPDCH: L3 signalling, AMR; TCP ACKs; 16 / 64 / 128 / 348 kbps

DPCCH: TPC, Pilot, TFCI


Fractional DPCH: F-DPCH (DL)

The Fractional DPCH (F-DPCH):

introduced in 3GPP Rel. 6 (enhanced in Rel. 7; NSN RU20 implementation based on Rel. 7)

replaces the DL DPCCH

includes Transmit Power Control (TPC) bits but excludes TFCI & Pilot bits & SRB TFCI bits - no longer required as there is no DPDCH Pilot bits - no longer required as TPC bits are used for SIR measurements

SRB mapped to E-DCH & HS-DSCH

increases efficiency by allowing up to 10 UE to share the same DL SF256 channelization code - time multiplexed one after another

RU20 feature RAN1201; requires Rel. 7 or newer UE HSDPA & HSUPA must be enabled Feature is licensed using an RNC ON/OFF license License CPC exists and its state is ON

Tx Off TPC

Slot #i

1 time slot 2560 chips

Tx Off

256

chips

FDPCHEnabled WCEL; 0 (Disabled), 1 (Enabled)


HSDPA RRM

HSDPA Principles








Associated UL DCH

Appendix


Summary

Characteristic RU10 RU20 RU30 RU40

HSDPA users per cell 64 72 (RAN1668) 72 128 (RAN2124)

Modulation QPSK/16QAM QPSK/16QAM & 64QAM

(RAN1643) QPSK/16QAM/64QAM QPSK/16QAM/64QAM

MIMO No Yes (2x2) (RAN1642) Yes Yes

Dual-Cell HSDPA No Yes (RAN1906) DC-HSDPA DC-HSDPA

DB DC HSDPA

(RAN2179)

Data rate per UE up to 14 Mbps up to 42 Mbps up to 42 Mbps 84 Mbps

(RAN 1907) up to 84 Mbps (RAN1907)

Traffic Classes Interactive + Background

+ Streaming

+ CS Voice over HSPA

(RAN1689) all traffic classes

all traffic classes

Packet Scheduler Proportional Fair (PF)

+ QoS Aware HSPA

Scheduling

PF + QoS aware

scheduling

PF + QoS aware

scheduling

PF + QoS aware

scheduling

HSDPA Multi-RAB multiple RAB HSDPA +

AMR

multiple RAB HSDPA +

AMR


AMR, +CS64 Conv.


AMR, +CS64 Conv.

Code Multiplexing (Scheduled users per TTI)

Yes (up to 3) Yes (up to 4) Yes (up to 4) Yes (up to 4)

UL associated DCH 16, 64, 128, 384 Kbps 16, 64, 128, 384 Kbps 16, 64, 128, 384 Kbps 16, 64, 128, 384 Kbps

DB: Dual Band


Most enhanced features must be licensed individually and are activated by setting individual off / on parameter

Some features can be activated on cell level, others on WBTS or even RNC level only

Feature Activation

HSDPAenabled WCEL; 0 = disabled; 1 = enabled

HSDPA48UsersEnabled RNFC; 0 = disabled; 1 = enabled

HSDPA64UsersEnabled WCEL; 0 = disabled; 1 = enabled

HSDPA14MbpsPerUser WBTS; 0 = disabled; 1 = enabled

HSDPAMobility Serving HS-DSCH cell change & SHO on/off switch

RNFC ; 0 = disabled; 1 = enabled

HspaMultiNrtRabSupport HSPA multi RAB NRT support

WCEL; 0 = disabled; 1 = enabled

HSDPADynamicResourceAllocation HSDPA Dynamic Resource Allocation

RNFC; 0 = disabled; 1 = enabled

HSDPA16KPBSReturnChannel HSDPA 16 Kbps UL DCH return channel on/off

RNFC; 0 = disabled; 1 = enabled

HSPA72UsersPerCell WCEL; 0 = disabled; 1 = enabled

if enabled, max. 72 HSDPA/HSUPA users can be

supported per cell.

HSPA128UsersPerCell WCEL; 0 = disabled; 1 = enabled

if enabled, max. 128 HSDPA/HSUPA users can be

supported per cell.

RU20/

30

HSDPA64QAMAllowed; MIMOEnabled;

DCellHSDPAEnabled; MIMOWith64QAMUsage


DCellAndMIMOUsage

WCEL; 0=DC-HSDPA and MIMO disabled; 1=DC-HSDPA and MIMO

w/o 64QAM enabled; 2=DC-HSDPA and MIMO with 64QAM enabled

FDPCHEnabled; CPCEnabled


HSPAQoSEnabled WCEL; 0..4; 1; 0 = disabled

0 = QoS prioritization is not in use for HS transport

1 = QoS prioritization is used for HS NRT channels

2 = HSPA streaming is in use

3 = HSPA CS voice is in use

4 = HSPA streaming & CS voice are in use

RU40


Cell Group Definition

SCHs under the same Node B should not overlap with each other

define for each sector offset relative to BTS frame number with parameter Tcell

Cells with offsets within certain range form one cell group Group 1 offset = 0-512 chips Group 2 offset = 768-1280 chips Group 3 offset = 1536-2048 chips Group 4 offset = 2304 chips

0 chips

256 chips

512 chips

BTS reference

SCH

BTS reference

SCH

BTS reference

SCH

Tcell Frame timing offset of a cell

WCEL; 0..2304 chips;

256 chips; no default


HSPA 72 / 128 Users per Cell (1/3)

72/128 users

72/128 users

72/128 users

Hardware requirements:

Flexi Node B must have Rel2 or Rel3 system module

HSPA72UsersPerCell

WCEL; 0 = not enabled; 1 = enabled

HSPA 72 users/cell: RAN1686 (RU20); HSPA 128 users/cell: RAN2124 (RU40); optional

RNC License Key required (On-Off)

increases the number of simultaneous HSPA users to 72 / 128 per cell both with dedicated & shared scheduler

HSDPA, HSUPA, Dynamic Resource Allocation must be enabled, Continuous Packet Connectivity & F-DPCH are recommended for both RAN1686 & RAN2124, HSUPA DL Physical Channel Power Control

recommended for RAN2124

max. 15 codes allocated (HS-PDSCH code set = 11010 10100 10000) Code multiplexing (max. no. of HS-SCCH codes MaxNbrOfHSSCCHCodes = 4)

HSDPA 16 Kbps UL DCH should be enabled to avoid UL overload

Other parameters may restrict max. number of

HSPA users, e.g.:

- WCEL: MaxNumberEDCHCell

- WBTS: MaxNumberEDCHLCG

- WCEL: MaxNumberHSDSCHMACdFlows

- WCEL: MaxNumberHSDPAUsers

- WCEL: MaxNumbHSDPAUsersS

- WCEL: MaxNumbHSDSCHMACdFS

- WCEL: MEHMaxHSDPAUsers

HSPA128UsersPerCell

WCEL; 0 = not enabled; 1 = enabled


DL Code allocation in a cell depends on activated features and traffic

if HSPA 72 Users Per Cell or HSPA 128 Users Per Cell is enabled, RNC allocates DL codes according to Maximum number of scheduled HSDPA user per TTI (Code Multiplexing) or Temporary maximum number of HSDPA users if Mass Event Handler is enabled (MEHMaxHSDPAUsers; WCEL; 0..128; 1; 30)

MaxNbrOfHSSCCHCodes; WCEL; 1..4; 1; 1 (4 is recommended in both cases)

1 E-RGCH & E-HICH codes is reserved in cell setup; max number of E-RGCH/E-HICH codes is 4 or not limited

reserved number of E-RGCH/E-HICH codes depend on number of HSUPA users, TTI (2ms or 10ms), whether the cell is serving or non-serving E-DCH cell to the UE, and scheduled or non-scheduled transmission

if Paging 24 kbps feature is enabled, more DL codes are needed to separate FACH and PCH traffic

PCH24kbpsEnabled; WCEL; on/off & NbrOfSCCPCHs; WCEL; 1..3; 1; 1

S-CCPCH

depending on

FACH / PCH

configuration

HS-SCCH

E-RGCH

E-HICH

HSPA 72 / 128 Users Per Cell (2/3) DL Code allocation

SF 16,0

SF 32

SF 64

SF 128

SF 256

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15


No. of HS-SCCH channels increased to 4 to schedule & control increased number of HSPA users in a cell

DL code space limited dynamic DL control channel allocation mechanism introduced to maximize available codes for HS-PDSCHs

HSUPA RRM (E-RGCH & E-HICH management / dynamic code allocation)

if code tree resources allocated like on previous slide, following traffic is supported: 15 codes @ SF16 for HSDPA

single user per 2 ms TTI (no code multiplexing)

MIMO enabled

F-DPCH enabled

most likely RNC will allocate another SF16 branch to increase control channel traffic reducing HSDPA SF16 codes further

Traffic analysis

HSPA 72 / 128 Users Per Cell (3/3) MaxNbrOf HSSCCHCodes WCEL; RU10 & earlier:

1..3; 1; 1; RU20: 1..4

Code allocation in

case of 4 HS-SCCH:


HSDPA RRM

HSDPA Principles



HSDPA Packet Scheduling Scheduling Types: Round Robin & Proportional Fair Scheduling & Code Multiplexing Basics of QoS Aware Scheduling and Application Aware RAN





Associated UL DCH

Appendix

How to incorporate App Aware RAN


Scheduler Types

Supports packet schedulers

Round Robin RR

Proportional Fair PF (requires individual license)

Type of scheduler set by HSDPA.BB.Resource.Allocation commissioning parameter

Round Robin Scheduler

assigns sub-frames in rotation

User at cell edge served as frequently as user at cell centre

does not account for channel conditions experienced by UE

Low total throughput in cell

if no data have to be transferred from Node B to certain UE then the sub-frame is assigned to the next one


Proportional Fair PF Scheduler (1/2)

TTI 1 TTI 2 TTI 3 TTI 4

USER 1 Es/N0 USER 2 Es/N0

Scheduled user

Takes into account multipath fading conditions experienced by UE

Improved total throughput in cell in comparison to round robin

Sub-frames assigned according scheduling metric Ratio instantaneous data rate / average data rate

experienced in the past

User at cell edge served less frequently as user at cell centre

Estimate of instantaneously supported

user throughput

Based on compensated CQI

Calculated average user throughput in the past

Throughput measured every 10 ms with 100 ms

sliding window

ave

inst

TP

TP


Round Robin RR scheduling

Max. total throughput 1100 Kbps Proportional Fair PF scheduling

Max. total throughput 1300 Kbps

Example:

Macro cell

5 codes for HSDPA Carrier shared with R99

Maximum total transmission power 20 W

Static HS-PDSCH + HS-SCCH power

Proportional Fair PF Scheduler (2/2)


Scheduling / HSDPA Code Multiplexing

UE1 UE2 UE3

Amount of

data in buffer

UE1 UE2 UE3

Full buffer Different data amounts

7

8

7

8

RU10 & later

15 codes 2

10

5

8

3

10

Codes & power are divided

optimally between users

depending on data amount.

MaxNbrOfHSSCCHCodes Max. number of HS-SCCH codes

WCEL; 1..4*; 1; 1

(no Code Multiplexing)

HSDPA Code Multiplexing: enables simultaneous transmission of up to 4* HSDPA UEs during 1 TTI

each simultan. served HSDPA UEs must have separate HS-SCCH

5 codes must be allocated to HS-PDSCH MAC-hs entity selects (3) best users (based on PF or QoS aware metric) for transmission in the next TTI

HS-PDSCH codes & power resources shared, taking into account: how much data user has in its buffer Channel conditions of user

* 3 before RU20


Basics of QoS Aware Scheduling

Shortcomings of standard PF PF metric does not distinguish between traffic classes

No bit rate guarantee, i.e. no streaming services supported

Interactive service not prioritised against background one

Idea of QoS aware HSPA scheduling (RAN1262) QoS aware HSPA scheduling enabled with parameter HSPAQoSEnabled

HSDPA dynamic resource allocation must be enabled

Streaming services

Guaranteed bit rate set by RNC

Interactive IA & Background BG services

Operator can set nominal bit rate (target minimum bit rate)

If not defined, service treated as best effort one

Operator can set service priorities, so that IA services are scheduled more often than BG ones

Services belonging to same traffic class again scheduled according PF HSPAQoSEnabled

WCEL; 0..2; RU20: 0..4;1; 0 = disabled

0 = QoS prioritization is not in use for HS transport

1 = QoS prioritization is used for HS NRT channels

2 = HSPA streaming is in use (RAN1004)

3 = HSPA CS voice is in use (RAN1689)

4 = HSPA streaming and CS voice are in use


Application aware RAN

IP IP/UDP

GTP - U

Inspection and inner IP packet Marking

IP

DPI DPI marks inner IP packet DSCP value based on

operator policies

FP MAC RLC

PDCP

GTPU

HSPDA scheduler

FP

SPI weight MAC - d

flows

Traffic type and/or

activity triggers change

of initial SPI (based on

DPI marking)

NodeB RNC

0

7

8

Same Bearer Same Bearer SPI - mod in FP

Change scheduling

weight associated with

the MAC-d flow

Application Aware RAN

Equips operators with QoS tools for typical terminals carrying multiple applications within one bearer with HSDPA allocated

Enables prioritization of the latency sensitive data by increasing the scheduling priority at the air interface and/or demotion of non-priority P2P traffic (priority drop = P2P traffic share down),

and introduces dynamic demotion of UL bulk traffic by the BTS

in a single RAB case

Applications requiring the same treatment at RAN are grouped by the operator into Application Groups (up to 6) characterized with AARConfigTable

(consisted of AppGrpId, DSCPCode1..5 (up to 5 applications per group),

Precedence, TargetSPIforSPI0..11)

Precedence value determines what SPI should be chosen when packets belonging to multiple application groups are detected by the RNC

(promote/demote/do nothing)

Shortcomings of available 3GPP QoS model:

not possible to differentiate QoE to UE using multiple applications within a NRT RAB i.e. to have micro-QoS within a fat pipe

AppAwareRANEnabled WCEL; Disabled (0), Enabled (1); 0

Precedence RNHSPA; 1..6; 1; 255 = not defined

AppGrpId RNHSPA; 1..6; 1; 255 = not defined

DSCPCode1..5 RNHSPA; 0..62; 1; 255 = not defined

TargetSPIforSPI0..11 RNHSPA; 0..11; 1; 255 = not defined


QoS Aware Scheduling and Application Aware RAN

Scheduling weights

For each combination of RAB QoS parameters operator can define service priority Traffic class Traffic handling priority THP Allocation & retention priority ARP

Service priorities & Scheduling Priority Indicators SPI Defined by multiple parameter QoSPriorityMapping For services on DCH service priorities just define values entering queuing and priority based scheduling

(see R99 PS)

For services on HS-DSCH/E-DCH or HS-DSCH/DCH services priorities define directly SPI It is initial SPI value if AppAwareRANEnabled = 1 (dynamic SPI based on the application type and initial

SPI value is set and communicated to BTS using CmCH-PI field in Frame Protocol)

If HSPAQoSEnabled is disabled but AppAwareRANEnabled = 1 then initial SPI for services with HSDPA can be configured by the operator with is defined by InitialSPINRT; RNHSPA; SPI 5 (5), SPI 6 (6); SPI 5 (5)

SPI mapped onto scheduling weights: define how often service of certain QoS parameter set scheduled in comparison to another one with

another QoS parameter set

PF scheduling extended by required activity detection RAD with delay sensitivity DS

Priority for Streaming traffic class with ARP1/2/3:

PriForStreamARP1/2/3 (RNC) (0..15) ( = 1) (13/13/13)

Priority for Interactive TC with THP 1 & ARP 1/2/3:

PriForIntTHP1ARP1/2/3 (RNC) (0..11) ( = 1) (11/11/11)





Priority for Background TC with ARP 1/2/3:

PriForBackARP1/2/3 (RNC) (0..11) ( = 1) (0/0/0) ARP: Allocation & retention priority

SPI: Scheduling priority indicators

THP: Traffic handling priority


QoS Aware Scheduling and Application Aware RAN Mapping QoS parameter for DCH

QoS parameter

RAB profile

Service

priority

Mapping defined

by QoSPriorityMapping

RNC PS

Queuing

Priority Based Scheduling

Mapping QoS parameter to scheduling weights for HS-DSCH/E-DCH or HS-DSCH/DCH

QoS parameter

RAB profile Service priority

Mapping defined

by QoSPriorityMapping

Node B PS:

Scheduling weight

modifying PF

SPI: Scheduling Priority Indicators

Mapping defined by

SchedulingWeightList

SchedulingWeightList is BTS commissioning parameter defining Mapping QoSPriorityMapping to SchedulingWeight

If AppAwareRANEnabled = 1 then dynamic SPI

setting based on the application type and initial SPI


QoS Aware Scheduling

Guaranteed Bit Rate GBR Set by RNC for streaming services on basis of the RAB profile

Nominal bit rate NBR = target minimum bit rate The nominal bit rate NBR is set as the target minimum bit rate in the RNC for NRT HS-DSCHs.

Can be specified by operator for NRT services Individually for each SPI 0..12 and Individually for UL and DL If Application Aware RAN is enabled SPI is dynamically modified by the RNC PDCP layer but the new NBR value

corresponding to the new SPI is not communicated to the BTS and BTS continues using the old NBR value. RNC ensures

that the SPI promotion/demotion for NBR users is performed within the SPI range defined for NBR users

NBR: Nominal Bit Rate

NBRForPri0..12UL UL NBR for Priority value 0..12 (structured

parameter)

RNC; RU30: RNHSPA; 0..2000 K; 8 K; 0 K for

all priority values

NBRForPri0..12DL DL NBR for Priority value 0..12

RNC; RU30: RNHSPA; 0..2000 K; 8 K; 0 K for

all priority values


HSDPA RRM

HSDPA Principles

HSDPA Protocols & Physical Channels



Basics of HSDPA Power Allocation HS-SCCH & HS-DPCCH Power Control Static & Dynamic HS-PDSCH Power Allocation



HSDPA Channel Type Selection and Switching

Associated UL DCH

Appendix


Overview HS-PDSCH High-Speed Physical DL Shared Channel

HS-SCCH Shared Control Channel for HS-DSCH

associated DCH* Dedicated Channel

HS-DPCCH Dedicated Physical Control Channel (UL) for HS-DSCH

Static power allocation

Tx power fixed Slowly adjusted in dependence on HS-SCCH Tx power

Dynamic power allocation

All power not needed for R99 services available for HSDPA

Slowly adjusted in dependence on R99 & HSDPA traffic

Fast power control in dependence on:

- CQI

- Feedback of UE

Fast power control parallel to DPCCH with offset for CQI

ACK/NACK

Inner loop PC basing DL TPC and CQI

WBTS UE

F-DPCH* Fractional Dedicated Physical Channel

* F-DPCH can be

allocated in DL only if

SRB can be mapped

to HSPA channels


Example:

PCPICH + = 6 W (37.8 dBm)

P0 = 0

CQI TBS Throughput CQI PHS-SCCH

4 317 159 K -7.7 dB (37.8 - 7.7) dBm = 30.1 dBm (1.0 W)

13 2279 1140 K -16.6 dB (37.8 - 16.6) dBm = 21.2 dBm (0.13 W)

HS-SCCH inner loop power control algorithm

Node B estimates HS-SCCH Tx power according to: PHS-SCCH = PCPICH + + CQI + P0

HS-SCCH Power Control (1/3)

PCPICH: CPICH power

measurement power offset (see section link adaptation)

CQI: power offset taken from CQICOMPENSATED by look up table (next slide)

P0: correction estimated by HS-SCCH outer loop power control algorithm

HS-SCCH Tx power Estimated for each HSDPA connection

individually

Updated with each CQI report



HS-SCCH outer loop power control algorithm

With each feedback (ACK or NACK) from UE Correction P0 decreased by 0.005 dB

But not below -2 dB (maximum power decrease by factor 1.6)

If there is no feedback from UE Correction P0 increased by 0.5 dB

But not above 4 dB (maximum power increase by factor 2.5)

ACK or NACK

No feedback

time

P0

0.005 dB

0.5 dB



0

2000

4000

6000

8000

10000

12000

14000

16000

18000

0 100 200 300 400 500 600 700 800 900 1000

HS-SCCH Tx Power (mW)

Oc

cu

ran

ce

s

PtxMaxHSDPA = 30 dBm



0

5000

10000

15000

20000

25000

30000

0 100 200 300 400 500 600 700 800 900 1000

HS-SCCH Tx Power (mW)

Oc

cu

ran

ce

s




Variance of HS-SCCH Tx power in relatively poor channel conditions

Variance of HS-SCCH Tx power in relatively good channel conditions

HS-SCCH Tx power increases in poor channel conditions

with higher HS-PDSCH Tx power

Link budgets typically assume 0.5 W HS-SCCH Tx power at cell edge

Static Power Allocation


Power offsets HS-DPCCH Tx power goes parallel to that of DPCCH

for ACK / NACK & CQI fields hardcoded power offsets in dependence on DPDCH data rate (16 / 64 / 128 / 384 K)

for UL link budgets ACK / NACK offset more important than CQI one

HS-DPCCH Power Control

DPCCH

DPDCH

Factor

2.7 dB for 16 K DPDCH

9.5 dB for 384 K DPDCH CQI ACK/NACK

HS-DPCCH


HS-PDSCH Power Allocation

Static Power Allocation Dynamic Power Allocation

PHSDPA PtxMaxHSDPA PHSDPA min(PtxMaxHSDPA, PtxCellMax)- power allocated to R99 DCH & DL control channels

Fixed load target PtxTargetHSDPA Dynamically adjusted load target PtxTargetPS

Fixed overload threshold for R99 Overload threshold for R99 goes parallel to load target:

PtxTargetHSDPA + PtxOffsetHSDPA PtxTargetPS + PtxOffset

In case of overload HSDPA might be In case of overload HSDPA power might be reduced,

released immediately but usually service not released immediately

Priorities distinguish between R99 & Priorities distinguish between interactive & background

HSDPA users only users as well

PtxMaxHSDPA Maximum allowed HSDPA power

WCEL; 0..50 dBm; 0.1 dB; 43 dBm

PtxTargetHSDPA Target for transmitted non-HSDPA power

WCEL; -10..50 dBm; 0.1 dB; 38.5 dBm

PtxOffsetHSDPA Offset for transmitted non-HSDPA power

WCEL; 0..6 dB; = 0.1 dB; 0.8 dB

HSDPADynamicResourceAllocation HSDPA Dynamic Resource Allocation

RNC; RU30: RNFC; 0 = disabled; 1 = enabled

PtxCellMax Cell maximum transmission power

WCEL; 0 .. 50 dBm; 0.1 dB; 43 dBm

PtxOffset Offset for transmitted power

WCEL; 0 .. 6 dB; 0.1 dB; 1 dB


Dynamic HS-PDSCH Power Allocation

Adjustable load target PtxTargetPS PtxTargetPSMin (minimum value)

PtxTargetPSMax (maximum value, also initial value, HS-RACH is set up in the cell)

PtxTargetPSMaxHSRACH (maximum value used if HS-RACH is set up in the cell)

PtxTargetPSMin Min DCH PS target for dynamic HSDPA pwr allocation

WCEL; -10..50 dBm; 0.1 dB; 36 dBm

PtxTargetPSMax Max DCH PS target for dynamic HSDPA pwr allocation

WCEL; -10..50 dBm; 0.1 dB; 40 dBm

PtxTargetPSMaxHSRACH Max DCH target power level with HS-RACH for dynamic HSDPA pwr allocation

WCEL; 0..40 dBm; 0.1 dB; 32767 dBm (Value set by the PtxTargetPSMax parameter used when the

HS-RACH has been setup in the cell)

PtxNC

PtxNRT

PtxHSDPA

PtxMax

PtxNonHSDPA

PtxTargetPSMin (36 dBm)

PtxTargetPSMax (40 dBm)

PtxTargetPS

PtxTargetPSMin -10..50 dBm; 0.1 dB; 36 dBm

PtxTargetPSMax -10..50 dBm; 0.1 dB; 40 dBm


HSDPA RRM

HSDPA Principles







HSDPA Channel Type Selection and Switching

Associated UL DCH

Appendix


Static & Dynamic Allocation (1/3)

HSPDSCHCodeSet

11010 10100 100000

HSPDSCHCodeSet

00000 10100 100000

HSPDSCHCodeSet

00000 00000 100000

Additionally required

HSDPADynamicResourceAllocation = enabled

Number of HS-

PDSCH codes (full

set)

HSDPA

15

Codes

HSDPA

10

Codes

Static

code

allocation

5 X X X

6 - - -

7 - - -

8 X X -

9 - - -

10 X X -

11 - - -

12 X - -

13 - - -

14 X - -

15 X - -



Dynamic code allocation applied if:

HSDPA dynamic resource allocation enabled (HSDPADynamicResourceAllocation)

Maximum number of codes > minimum number (HSPDSCHCodeSet)

BTS capable of 10/15 codes

HSDPA service starts with minimum number of codes defined by HSPDSCHCodeSet

Cell-specific scheduler reserves HS-SCCH codes from the spreading code tree according to MaxNbrOfHSSCCHCodes

If HSDPA dynamic resource allocation disabled, 5 codes are available only

SF=8

SF=4

SF=2

SF=1

SF=16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

HS - PDSCH

. .

SF=8

SF=4

SF=2

SF=1

SF=16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

HS - PDSCH Rel - 99 channels (& HS - SCCH)

Rel - 99 code area (& HS - SCCH)

Shared code area

Dedicated HS - PDSCH

SF=8

SF=4

SF=2

SF=1

SF=16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

HS - PDSCH

. .

SF=8

SF=4

SF=2

SF=1

SF=16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

HS - PDSCH Rel - 99 channels (& HS - SCCH)

Rel - 99 code area (& HS - SCCH)

Shared code area

Dedicated HS - PDSCH code area



128 128 128

Available CC Allocated CC Blocked CC

SF16

SF32 32

SF64 64 64 64

SF256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256

128 128 128 128 128 128 128 SF128

+14 x SF16

HS-PDSCH

CPICH AICH

S-CCPCH1

S-CCPCH2 HS-SCCH HS-SCCH HS-SCCH

32

64 64

256 256 256 256 256 256 256 256

128 128 128 128

SF16

E-RGCH E-HICH

E-AGCH

Maximum of 14 HS-PDSCH codes possible with 3 HS-SCCH & HSUPA

P-CCPCH PICH


HSDPA RRM HSDPA Principles




Basic of HSDPA Power Allocation


Basics of HSDPA Mobility Serving Cell Change Inter-RNC Mobility Cell Re-selection Inter-frequency Mobility Directed RRC Connection Setup


Associated UL DCH

Appendix


Parameter Templates

FMCS/I/GId identifies parameter set for intra-, inter-frequency & inter-

system measurements

FMCS/G/I; 1..100; 1; no default

HSDPAFMCS/I/GIdentifier Identifies FMCS/I/G parameter set to be applied for a HSDPA

service within a certain serving cell

WCEL; 1..100; 1; no default

RTwithHSDPAFMCS/I/GIdentifier HSDPA FMCS/I/G identifier for AMR multi-service

WCEL; 1..100; 1; no default

Identifies FMCS/I/G parameter set to be applied for a HSDPA

+ AMR multi-RAB service within a certain serving cell

S:Intra- Frequency

I:Inter- Frequency

G:Inter- System

WCELL

ADJG / L

ADJI

ADJS

WBTS

RNC

FMCS

FMCI

FMCG

100

100

100

HOPS 100

HOP I 100

HOPG 100

32

48

32

ADJD

HOPS 100

32

HOPSId HOPS identifier: identifies parameter set for intra-frequency mobility

HOPS; 1..100; 1; no default

HSDPAHOPSIdentifier ADJS; 1..100; 1; no default

identifies parameter set to be applied for a HSDPA service to move

to a certain adjacent cell

RTwithHSDPAHOPSIdentifier HSDPA HOPS identifier for AMR multi-service

ADJS; 1..100; 1; no default

RNFC

RNMOBI


HSDPA Mobility

Serving Cell Change SCC (1/3): Candidate

Initial cell selection

1 cell active only: just attempt to establish service

More than 1 cell active Initial selection of Serving Cell based on latest reported Ec/I0

To be candidate, HSDPA capable cell must fulfil following condition:

Serving cell is chosen in order of EC/I0

If allocation of HS-DSCH fails due to any reason, next best candidate cell is attempted

EC/I0 (active cell*) EC/I0 (best cell) HSDPAServCellWindow

HSDPAServCellWindow CPICH Ec/Io window for serving HS-

DSCH cell selection

RNC, RU30:RNMOBI; 0..6; 0.5; 2 dB

* Serving Cell

Max. allowed difference between the best cell in the Active Set & the Serving HSDSCH cell.

If Serving HS-DSCH cell out of this window Serving HS-DSCH cell change procedure initiated.

Methods to handle HSDPA mobility

Serving HS-DSCH cell change

Cell reselection with HS-DSCH - FACH channel type switching ( Appendix)

HSDPAMobility Serving HS-DSCH cell change & SHO on/off switch

RNC, RU30:RNFC; 0 = HSDPA cell reselection

1 = Serving HS-DSCH cell change


Serving Cell Change (2/3): Ec/Io based Periodical Intra-frequency EC/I0 measurements started when:

HS-DSCH MAC-d flow active AND Active set size > 1 (event 1a) Measurements stopped if either of the above criteria not true

CPICH EC/I0 measurement reporting by UE: Higher layer filtering for measurement results before reporting by

EcNoFilterCoefficient

Periodical reporting with reporting interval defined by HSDPACPICHReportPeriod

RNC averages reports over HSDPACPICHAveWindow

EC/I0 based Serving Cell change triggered if: Ec/I0 (server) < EC/I0 (best cell) HSDPAServCellWindow AND

EC/I0 (server) < HSDPACPICHEcNoThreshold

EcNoFilterCoefficient FMCS; k = 0..6; 1; k = 3

HSDPACPICHReportPeriod RNC, RU30:RNMOBI; 0.25,

0.5, 1, 2, 3, 4, 6, 8, 12; 0.5 s

HSDPACPICHAveWindow RNC, RU30:RNMOBI; 1..10; 1; 3

Addition

window

CPICH 1

CPICH 2

EC/I0

time New cell

detected

Periodic

reports

Serving cell change

EC/I0 threshold

Serving cell change

triggered

periodic reports as long

process is running

HSDPAServCellWindow Serving Cell change window

RNC, RU30:RNMOBI; 0..6; 0.5; 2 dB

HSDPACPICH

EcNoThreshold RNC, RU30: RNHSPA;

-20..0; 0.5;-5 dB


Serving cell

change triggered

Serving Cell Change (3/3): SIR error based

SIR error based Serving Cell change triggered if:

SIRerror (Server) < HSDPASIRErrorServCell

SIRerror

time

Periodic reports as long

HSDPA service running

Serving cell change

SIRerror threshold

HSDPA service

established

HSDPASIRErrorServCell RNC, RU30: RNMOBI; -10..0; 0.5; -3 dB

for Inter Node B & intra Node B inter-LCG cell change (not applicable for intra Node B inter-LCG )

Periodical SIR error measurements started when HS-DSCH MAC-d flow active difference between actual SIR & SIRtarget: SIRerror = SIR SIRtarget

Measurement reporting by Node B Higher layer filtering for measurement results before reporting by

HSDPASIRErrorFilterCoefficient

Periodical reporting with reporting interval defined by HSDPASIRErrorReportPeriod (if set to 0 SIR measurement

is not used as criteria for SCC)

RNC averages reports over HSDPASIRErrorAveWindow

HSDPASIRErrorFilterCoefficient RNC, RU30: RNMOBI; k = 0..10; 1; 5

HSDPASIRErrorReportPeriod RNC, RU30: RNMOBI; 0..10; 0.5; 0.5 s

HSDPASIRErrorAveWindow RNC, RU30: RNMOBI; 1..10; 1; 3


HSDPA RRM

HSDPA Principles HSDPA Physical Channels RU40 Capabilities & Baseband Configuration HSDPA Packet Scheduling Basics of HSDPA Power Allocation Basics of HSDPA Code Allocation Basics of HSDPA Mobility HSDPA Channel Type Selection Associated UL DCH Appendix


HS-DSCH selected in case of Capacity Request if all of the following conditions are met:

1) Traffic class & THP allowed on HS-DSCH: configurable with HSDSCHQoSClasses

2) UE supports HS-DSCH

2) Cell supports HSDPA & HS-DSCH is enabled

3) Multi-RAB combination of UE supported with HS-DSCH HSDPA + AMR to be enabled with AMRWithHSDSCH

HSDPA + R99 NRT + AMR / R99 streaming enabled with

HspaMultiNrtRabSupport

5) No. of simultaneous HS-DSCH allocations in BTS/cell below max. no. supported by base band configuration

6) HsdschGuardTimerHO & HsdschGuardTimerLowThroughput guard timers not running for UE

7) UE not performing inter-frequency or inter-system measurements

8) Active set size = 1 if HSDPAMobility = disabled

9) If HSDPA dynamic resource allocation disabled and no existing MAC-d flow in the cell PtxNC PtxtargetHSDPA for HSDPAPriority = 1 PtxnonHSDPA PtxtargetHSDPA for HSDPA Priority = 2

10) UE does not have DCHs scheduled with bit rates higher than zero

11) HS-DSCH physical layer category is supported

12) HS-DSCH can be admitted if PS streaming and CS voice RB resource are utilized

13) HSDPA prevention function of the RAN2879: Mass Event Handler feature does not prevent from HS-DSCH allocation

HSDPA prevention is started if RNC starts using the prioritized DL power AC for AMR CS DCH speech call

Channel Type Selection CTS

HSDSCHQoSClasses HS-DSCH QoS classes

RNC, RU30: RNHSPA; 11111 =

background / interactive with THP

1/2/3 / streaming allowed

AMRWithHSDSCH Usage of AMR service with HS-DSCH

RNC, RU30: RNFC; 0 = disabled; 1 =

enabled

HspaMultiNrtRabSupport HSPA multi RAB NRT support

WCEL; 0 = disabled; 1 = enabled

THP: Traffic Handling Priority

HsdschGuardTimerHO

HS-DSCH guard time after switching to DCH

due to HO

RNC, RU30: RNHSPA; 0..30 s; 1 s; 5 s

HSDSCHGuardTimerLowThroughput

HS-DSCH guard timer due to low throughput

RNC, RU30: RNHSPA; 0..240 s; 1 s; 30 s


HSDPA RRM

HSDPA Principles







HSDPA Channel Type Selection & Switching

Associated UL DCH Bit Rates Packet Scheduling

Appendix


UL Return channel - Bit Rates

RB mapped onto HS-DSCH in DL DCH (or E-DCH) allocated as UL return channel

data rates for UL DCH return channel: 16, 64, 128 &384 kbit/s independent on R99 settings

16, 64, 128 kbit/s if PS streaming is mapped on HS-DSCH

16 kbps UL DCH return channel*: HSDPA16KBPSReturnChannel

HSDPAminAllowedBitrateUL: min. allowed bit rate -> this parameter is also used to limit UL DCH date rate if RAN2879 Mass Event Handler is used

PS: HS-DSCH (DL)

PS: DCH (UL)

PS: HS-DSCH (DL)

PS: DCH (UL)

HSDPA16KBPSReturnChannel RNC, RU30: RNFC; 0 = disabled;

1 = enabled

* optional feature RB: Radio Bearer

HSDPAminAllowedBitrateUL Min. bit rate for HSDPA a-DCH

RNC , RU30: RNHSDPA, RU40:WAC; 16 K, 64 K, 128 K, 384 K


Packet Scheduling: HSDPA with UL associated DCH HS-DSCH allocation triggered by UL:

high traffic volume indicated RNC tries to allocate return channel with highest possible bit rate low traffic volume indicated RNC tries to allocate return channel with initial bit rate

HS-DSCH allocation DL triggered: RNC tries to allocate HSDPAinitialBitrateUL

Direct DCH to HS-DSCH switch UL a-DCH bit rate can be same

as existing DCH UL bit rate

initial bit rate cannot allocated HS-DSCH not possible UL/DL DCH

HSDPAinitialBitrateUL

Initial bit rate for HSDPA a-DCH RNC, RU30: RNHSPA, RU40: WAC;

16 K, 64 K, 128 K, 384 K

Capacity Request

(TVMHigh)

64

kbps

384

128

t

0

Capacity Request

(TVM Low)

Initial bitrate

64 kbps

Decrease of the retried

NRT DCH bitrate

PBS

RT-over-NRT

t 1 t 2 t 3 t 5

16

t 4

Example

Initial bit rate = 64 K

Minimum bit rate = 16 K

Capacity Request

(TVMHigh)

Min. bitrate

16 kbps

UL a-DCH functionalities: PBS & overload control Decrease of retried NRT DCH bit rate RT over NRT Throughput based optimization Upgrade of NRT DCH data rate (normal or flexible)

DynUsageHSDPAReturnChannel

Dynamic usage of UL NRT a-DCH

HSDPA return channel

RNC, RU30: RNFC, ; 0 or 1; 0 = disabled

enabled by

TVM: Traffic Volume Measurement


HSDPA RRM HSDPA Principles








Associated UL DCH

Appendix: Static HS-PDSCH Power Allocation

Cell Reselection


Static HS-PDSCH Power Allocation (1/2)

Required parameter settings Dynamic HS-PDSCH power allocation disabled Fixed HS-PDSCH power defined with PtxMaxHSDPA

Rules for HSDPAPriority = 1 (higher priority for HSDPA) A: 1st HSDPA users enters cell

Non-controllable traffic PtxNC PtxTargetHSDPA HSDPA allowed Otherwise R99 only

HSDPA already active R99 scheduled up to PtxTargetHSDPA

B: Overload for total R99 traffic PtxnonHSDPA > modified overload threshold Standard R99 overload actions

C: Overload for PtxNC > modified overload threshold HSDPA released

Max power Node B Tx power

A

PtxOffsetHSDPA PtxnonHSDPA

PtxNC

PtxTargetHSDPA

B

Ptxtotal

PtxTarget

C

HSDPAPriority 1,2; 1 = HSDPA priority


-10..50 dBm; 0.1 dB; 38.5 dBm


0..6 dB; 0.1 dB; 0.8 dB

PtxMaxHSDPA Maximum allowed HSDPA power

WCEL; 0..50 dBm; 0.1 dB; 43 dBm


Static HS-PDSCH Power Allocation (2/2)

Rules for HSDPAPriority = 2 (higher priority for R99) A: 1st HSDPA users enters cell Total R99 traffic PtxnonHSDPA PtxTargetHSDPA Can have HSDPA Otherwise can have R99 only

HSDPA already active R99 scheduled up to PtxTargetHSDPA

B: Overload for total R99 traffic PtxnonHSDPA > modified overload threshold HSDPA released

C: Standard overload for total R99 traffic PtxnonHSDPA > standard overload threshold Standard R99 overload actions

Max power

Node-B Tx power

PtxOffsetHSDPA

PtxnonHSDPA

PtxNC

PtxTargetHSDPA

Ptxtotal

PtxTarget

PtxOffset

A B C

HSDPAPriority 1,2; 1 = HSDPA priority


-10..50 dBm; 0.1 dB; 38.5 dBm


0..6 dB; 0.1 dB; 0.8 dB


HSDPA RRM

HSDPA Principles







HSDPA Channel Type Selection & Switching

Associated UL DCH

Appendix: Static HS-PDSCH Power Allocation

Cell Reselection


Cell Re-selection (1/3)

HSDPAMobility set to disabled IF- mobility handled by HSDPA Cell Reselection, not by serving cell change IF- / IS- mobility handled by same events as for serving cell change

HSDPA cell reselection Transition to CELL_FACH based on event 1a Handling depends on setting of EnableRRCRelease

if disabled 1a triggers transition to Cell_FACH immediately if enabled 1a triggers IF- measurements only; transition to cell_FACH triggered by release margins

EnableRRCRelease

Enable RRC connection release

HOPS; 0 = disabled; 1 = enabled

HSDPARRCdiversity

SHO of the HSDPA capable UE

RNC, RU30: RNHSPA; 0 = disabled; 1 = enabled

HSDPARRCdiversity can disable SHO for stand alone SRB of HSDPA capable UE (e.g. according addition window)

reduces capacity consumption due to stand alone RRC connections (more capacity available for HSDPA)

if conditions for HSDPA mobility fulfilled, SHO for stand alone SRB is allowed in any case (e.g. triggered by release margins)

HSDPAMobility

Serving HS-DSCH cell change & SHO on/off switch

RNC, RU30: RNFC; 0 = HSDPA cell reselection;

1 = Serving HS-DSCH cell change

IF: Interfrequency

IS: Intersystem


time

Ec/Io

CPICH 2

Addition

Time

Measurement Reports

Addition Window

CPICH 1

HSDPA CELL_FACH HSDPA

EnableRRCRelease = disabled

Risk of ping-pong

But UE connected mostly to optimum cell

AdditionWindow

FMCS; 0..14.5 dB; 0.5 dB; 4 dB

Recommended 0 dB



time

Ec/Io

CPICH 2

Measurement Reports

CPICH 1

HSDPA CELL_FACH

ReleaseMarginAverageEcNo ReleaseMarginPeakEcNo One margin need to be exceeded only

HSDPA


EnableRRCRelease = enabled

No ping-pong

But UE often connected to non optimum cell

Addition

Time

Addition Window

ReleaseMarginAverageEcNo Release margin for average Ec/Io

HOPS; -6..6; 0.1; 2.5 dB

ReleaseMarginPeakEcNo Release margin for peak Ec/Io

HOPS; -6..6; 0.5 dB; 3.5 dB

09_RN31639EN40GLA0_RANPAR1_HSDPA_RRM_v1.1_RU40

Documents

Transcript of 09_RN31639EN40GLA0_RANPAR1_HSDPA_RRM_v1.1_RU40