2_HSDPA Theory Course Vers4

5/21/2018 2_HSDPA Theory Course Vers4

1/124Customer ConfidentialNon Binding

1 2006 Nokia HSDPA Theory Course V3.ppt / 2006-07-05 /BeAs

HSDPA Theory Course
http://c/USERS/RN2.1-RAN05%20INFORMATION/HSDPA%20Theory%20Course/Orange%20UK%20Material/Agenda.ppt


2/124

Customer ConfidentialNon Binding2 2006 Nokia HSDPA Theory Course V3.ppt / 2006-07-05 /BeAs

Module 1About HSDPA

Module 2Air Interface Module 3Effect of HSDPA Power on Throughput

Module 4Setting HSDPA Parameters

Module 5BTS

Module 6IUB

Module 7RNC

Training modules


3/124


Module 1About HSDPA

After the module the participant will be able to:

Explain what HSDPA is

Explain the benefits of HSDPA

Explain how HSDPA works on a high level


4/124


Operator Benefits

Improved packet data capacity of NW, enhanced spectral efficiency

Better usage of the radio network HW

Increased revenues through more users and usage

Improved Iub efficiency

Large scale resource reuse: License, Core NW, RNC, transmission, NodeB,

sites (DL cell size), feeders, antennas


5/124


Increased bit rates

Shorter service response times

Improved quality of end user experience

Better availability of services

User Benefits


6/124


Introduction

HSDPA = High Speed Downlink Packet Access

Part of 3GPP release 5 specifications

System of new physical channels for UTRAN

Downlink data rates up to 14.4 Mbit/s per user

Backwards compatible with earlier 3GPP releases


7/124


HSDPA

HSDPA increases data capacity with the introduction of

optimised features that are only available to packet dataservices

Why Downlink?

Data service is normally asymmetric in nature Downlink demand for resources is normally higher than in the uplink


8/124


Introduction

Fixed SF16 multicode transmission

Adaptive modulation and coding with QPSK and 16QAM

Shorter and static TTI length = 2 ms

NodeB based packet scheduling and H-ARQ retransmission

MAC-hs protocol in NodeB

Whats New in HSDPA 1/2:


9/124


Introduction

Whats New in HSDPA 2/2:

Parameter Improvement action Design features

Peak data rate Allocate more resources to

one user

Use excess link budget

Improve retransmission

Multicode transmission

Higher modulation (16QAM)

Hybrid ARQ

Cell throughput Use wasted power

Make the pipe bigger

Improve retransmission

Exploit multiuser diversity

Adapt rate to power

Higher modulation (16QAM)

Hybrid ARQ

Clever scheduling algorithm (optional)

Round trip time Make smaller packets

Retransmit faster

TTI reduction

NodeB-based retransmission


10/124


HSDPA Usage

NRT trafficRT traffic

Conversational Streaming Interactive Background

AMRLC

AMRLC

TMRLC

DCH

UMRLC

DCH

TMRLC

DCH

UMRLC

DCH

AMRLC

DCH RACH/FACH DCH/DCHDCH/HS-DSCH

PS domainCS domain


11/124


Cell

BroadcastCentre

HSDPA General Functional Division

Iur

Iu-CS

M

GW

MSC

VLR

HL

R

S

G

S

N

G

G

S

N

GMSC

Iu-PS

Iu-PS

Core NetworkRAN

Iu-CS

UE

NodeB

Iub

Iub

Iub

RNC

RNC

Iu-BC


12/124


UE Terminal 1

UE Terminal 2

L1 Feedback

CQI, Ack/Nack, TPC

L1 Feedback

Data

Data

Fast scheduling donedirectly by Node B (BTS)based on knowledge of:

- UE's channel quality -CQI- UE's capability- QoS demands

- Power and code resourceavailability

HARQ retransmissions

Modulation/Codingselection

Users may be time and/or code multiplexed

HSDPA General Principle


13/124


HSDPA Protocol Model

TNL

MAC-d

DCHFP

DCHFP

MAC-d

TNL

NodeB Iub RNC

RLC RLC

MAC-hs

PHY PHY TNL

MAC-d

MAC-hs HS-DSCH FP HS-DSCH FP

MAC-d

TNL

UE Uu NodeB Iub RNC

RLC RLCMAC-d flow

HS-DSCH

PHY PHY

UE Uu

DCH

DPCH

HS-PDSCH

R99

R5


14/124


NodeB

RNC

Rel99 DCH/DSCH Rel5 HS-DSCH

Packet

Retransmission

RLC ACK/NACK

First PhaseRetransmission

L1 ACK/NACK

Packet

In previous RNC releasesthe retransmission hasalways occurred from theRNC RLC.

Retransmission has beenbased on the RLCSequence Numbers Second PhaseRetransmission

Two phase retransmissionconcept

First phase retransmissionfrom BTS => HARQ

Second phaseretransmission from RNC ifthe first phase turned out tobe unsuccessful.

R99 vs. R5


15/124


Server RNC Node-B

UE

RLC retransmissionsTCP retransmissions

MAC-hs retransmissions

Retransmissions in HSDPA

HSDPA introduces L1 H-ARQas the first step retransmissionalong with the existing RLC

ARQ.

For TCP traffic additional

retransmissions (TCPretransmissions) occur on theapplication level
http://c/USERS/RN2.1-RAN05%20INFORMATION/HSDPA%20Theory%20Course/Orange%20UK%20Material/Support%20material%20for%20Orange%20UK%20course.ppt


16/124


Channels Allocated to One HSDPA User

UE

NodeB

Associated

DPCH

Associated

DPCH

1-15xHS-

PDSC

H

1-4xHS-

SCCH

HS-DPC

CH

Associated DPCH: Associated DedicatedPhysical Channel (UL/DL)

1 DPCH is required for each HSDPA UE

Signalling, Uplink data

HS-PDSCH: High-Speed PhysicalDownlink Shared Channel (DL)

Actual HSDPA data for HS-DSCHtransport channels

1-15 codes per channel

QPSK or 16QAM modulation HS-SCCH: High Speed Shared Control

Channel (DL) Informs the UE how and when to

receive the HS-PDSCH

HS-DPCCH: High Speed Dedicated

Physical Control Channel (UL) MAC-hs ACK/NACK information Channel Quality Information (CQI)
http://c/USERS/RN2.1-RAN05%20INFORMATION/HSDPA%20Theory%20Course/Orange%20UK%20Material/Support%20material%20for%20Orange%20UK%20course.ppt


17/124


HS-SCCH Information (DL)

CCS - Channelisation Code Set - spreading factor codes and code offset

MT - Modulation TypeQPSK or 16QAM

TBS - Transport Block Sizesize of transport block being sent to UE

HAP - Hybrid-ARQ Parameters - H-ARQ process number that the data belongs to

RV/CV - Redundancy or Constellation Version - RV starts at zero NDI - New Data Indicator - toggled for a new transmission. Same if retransmission

H-RNTIHigh Speed Radio Network Temporary Identity. Identifies UE data meant for

CRCCyclic Redundancy CheckError detection

2ms (after coding and puncturing)

H-RNTI mask

MT

1 bit

CCS

7bitsSF128,1

NDI

1 bit

RV/CV

3 bits

HAP

3 bits

TBS

6 bits

CRC

16 bits

H-RNTI mask

2nd and 3rd subframe1st subframe


18/124


HS-DPCCH Information (UL)

CQI information for Downlink20 Bits

H-ARQ10 Bits

Channelcoder

H-ARQ

Ack/Nack

Ack: All 1s

Nack: All 0s10 bits

Channelcoder

CQI value0-30

5 bits

CQI + Parity20 Bits

30 Bits


19/124


Timing Relationships.

14131211109876543210HS-SCCHDL Tx

Pkt 5Pkt 4Pkt 3Pkt 2Pkt 1HS-PDSCH

Received at UE

Propagation delay over the Air Interface

Pkt 1 Ack/NackHS-DPCCH

UL Tx from UE

7.5 Slots = 5ms = 19200 chips

14131211109876543210P-CCPCH

Broadcast DL Tx 3 slots = 2ms

10ms

2ms = 1 TTI

Pkt 5Pkt 4Pkt 3Pkt 2Pkt 1HS-PDSCHDL Tx 2 slots

1 TTI = 2ms


20/124


HARQ &CodingFlow Control

New NodeB HSDPA Functionality

User EquipmentNode BRNC

Buffer & Scheduler : Buffering of data, Terminal scheduling, Coding &Modulation selectionQPSK is still used and a new modulation type16QAM introduced

HARQ, Retransmission Handling and coding

Uplink Feedback Decoding

Flow Control towards the SRNC

PacketsBuffer &Scheduler

ACK/NACK &

Feedback

Decoding

16QAM

modul.


21/124


User equipmentNode BRNC

Packets

Flow Control

New terminal functions:

16 QAM demodulation

HARQ decoding and Retransmissions Handling

Soft buffer & combining

Fast Uplink Feedback Generation & encoding

New UE HSDPA Functionality

Soft buffer

&combining

ACK/NACK

&

Feedback

generation

QPSK/16QAM

demodulation

HARQ

decoding


22/124


Modulation

QPSK

2 bits / symbol

480 kbit/s / HS-PDSCH

max. 7.2 Mbit/s

10 00

0111

Q

I

Q

1011 1001

10001010

0001 0011

00100000

0100 0110

01110101

1110 1100

11011111

I

16QAM

4 bits / symbol

960 kbit/s / HS-

PDSCHmax. 14.4 Mbit/s


23/124


Adaptive Modulation

Node B

3) Adjust modulationscheme accordingto feedback received

from the UE

Good radio conditions use higher order modulation Increased throughput

UE


24/124


Hybrid ARQ (HARQ)

Hybrid ARQ is an implicit link adaptation technique using

adaptive modulation techniquesAdaptive Modulation uses C/I or similar measurements to set

the modulation scheme

Physical layer acknowledgements are used to make

retransmission decisions Hybrid ARQ adapts independently to the instantaneous

channel conditions

1/7


25/124


2/7Hybrid ARQ (HARQ)

Adaptive modulation (QPSK or 16QAM) provides coarse data

rate selection Hybrid ARQ provides fine data rate adjustment based on the

channel conditions (codes and TBS)

HARQ is implemented in the UE by using Chase Combining or

Incremental Redundancy


26/124


Hybrid ARQ (HARQ) 3/7

Node B

Ack

P1Nack

P2

Ack

P5Ack

P2

Ack

P3Ack

P4

P1

P3

P4

P5

P2

There is a delay of 7,5 slots or 2.5 TTIs between the UE receivingthe data packet and the Ack/Nack response message from the UE

P2


27/124


Turbo Coding

Turbo interleaving

Convolutionalcoder

Puncturing

Convolutionalcoder

bits inS

P1

P2

S1

S

P1

P2

1:2

1:1

1:2

3:2

Turbo Coding is best suited to delay tolerant non real timeapplications

Turbo Coding Rate = 1:3

4/7


28/124


Turbo encoder coding rate = 1/3.

Rate Matching is used to adapt to

the desired coding rate either by

using puncturing or repetition.

In the example, RM punctures into

rate 3/4.

Data to be

transmitted

Rate Matching

System bits

Parity 1

Parity 2

Turbo Encoder

Parity bitsare added

Rate Matching (Puncturing)

System bits

Parity 1

Parity 2

Data is ratematched 3:4(3 System bitsplus 1 parity bit)

5/7

H b id ARQ (HARQ) Ch C bi i /


29/124


System bits

Parity 1

Parity 2

Turbo Encoding of data

Hybrid ARQ (HARQ): Chase Combining


System bits

Parity 1

Parity 2

Original transmission

Chase Combining at Receiver (info retained in mobile receive buffers)

System bits

Parity 1

Parity 2

Recovered Data

System bits

Parity 1

Parity 2

System bits recovered successfully

Retransmission Retransmitteddata is exactlythe same asThe originaltransmission

6/7

Note: Recovery of the

system bits is moreimportant than the

parity bits as system

bits are the user data

H b id ARQ (HARQ) I t l R d d 7/7


30/124


Hybrid ARQ (HARQ): Incremental Redundancy

System bits

Parity 1

Parity 2

Turbo Encoder


System bits

Parity 1

Parity 2

Original transmission Retransmission

Incremental Redundancy Combining at Receiver (info retained in mobile receive buffers)

System bits

Parity 1

Parity 2

Recovered Data

System bits

Parity 1

Parity 2

System bits recovered successfully

7/7

Note: Recovery of the

system bits is moreimportant than the

parity bits as system

bits are the user data

Li k Ad t ti d P C t l


31/124


Link Adaptation and Power Control

HS-DSCH link adaptation has two loops

A) Inner loop based on CQI reports from UE (NodeBUE)

B) Outer loop in Node-B to control the BLER of the inner loop (RNCUE)

HS-SCCH power control has two loops

A) Inner loop based on the fast power control commands from UE (NodeBUE)

B) Outer loop in Node-B to control the BLER of the inner loop (RNCUE)

These algorithms are not standardized

HS-DSCH link adaptation

HS-SCCH power control

Do nlink HSDPA Code Allocations
http://c/TEMP/Support%20material%20for%20Orange%20UK%20course.ppt


32/124


Downlink HSDPA Code Allocations

15 Codes assigned to the HS-PDSCHs from SF16,1...SF16,15 (3GPP)

SF 128 assigned to the HS-SCCH (3GPP) Maximum of 5 codes/user is supported in RAS05/RN2.1

HS-PDSCH code resources are assigned to one user at a time

HS-PDSCH

SF=1

SF=2

SF=4

SF=8

SF=16

SF=32

SF=64

SF=128

SF=256

CPICH P-CCPCH

S-CCPCH

HS-SCCH

S-CCPCH

Free code that can beallocated to e.g. DPCH,HS-PDSCH (SF16) or HS-SCCH (SF128).

Code that cannot beallocated due to allocationslower in the code-tree /branch.

Code reserved for acommon channel.

Legend:

UMTS 3GPP R99
http://c/TEMP/Support%20material%20for%20Orange%20UK%20course.ppt


33/124


UMTS - 3GPP R99

Transmit

Power

Time

Maximum Allowed Transmit Power = PtxTarget

Overhead Channels

Power Controlled User Traffic Channels

Unused/Available Power

HSDPA 3GPP R5


34/124


HSDPA3GPP R5

TransmitPower

Time

Maximum Allowed Transmit Power = PtxTarget

Overhead Channels


Unused Power available for HSDPA use

Not all this unused power will

be used for HSDPA. The power

that may be used is operator

configurable

HSDPA (TDM Mode)


35/124


HSDPA (TDM Mode)

Transmit

Power

Time

Maximum AllowedTransmit Power = PtxTarget

Overhead Channels


UE-1 UE-2 UE-3 UE-4 UE-1 UE-3 UE-2 UE-1 UE-4

1-TTI2ms

2ms

HSDPA (CDM Mode)


36/124


HSDPA (CDM Mode)

TransmitPower

Time

Maximum AllowedTransmit Power = PtxTarget

Overhead Channels


UE-1UE-2

UE-3UE-4

UE-1UE-2UE-3

UE-4 UE-1 UE-2UE-3

UE-4UE-1UE-2

UE-3UE-4UE-1

UE-2UE-3UE-4

1-TTI2ms

2ms

SchedulersExample - not specific to

Nokia implementation


37/124


Schedulers

The scheduler schedules the information that will be sent from the Node B to the UE.

The scheduler requires important information from the uplink HS-DPCCH and other sources

Scheduler algorithm implementation is vendor specific

Scheduler

QoS and Subscriber ProfileWho is the subscriber? Platinum, Gold,Silver, Normal.What type of service is thesubscriber allowed? High priority, Besteffort

Uplink FeedbackCQI and Ack/Nackinformation

Node B buffer statusHow much data is in bufferHow fast is the data arriving

User HistoryHow long has userbeen waiting

Traffic ModelWhat type of traffic model shouldbe used - according to periodof the dayPeak/Off Peak

Available Radio ResourcesPowerCodes

UE CapabilitySee UE categories

Users are scheduled according to therequirements for transmission by theNode B over the air interface

Nokia implementation

Round Robin Scheduler


38/124


Simplest form of scheduler First in First out principle

Advantages:

Easy to implement

Minimises waitingtime

Increases effectivethroughput

Disadvantage:

Throughput notoptimised thereforethroughput is less

than maximumpossible throughput

UE 1 Datasent

UE 2 Datasent

UE 1

UE 6

UE 5

UE 4

UE3

UE 2

UE 3 Datasent

UE 4 Datasent

UE 5 Datasent

UE 6 Data

sent

UE 1 DataRequest

UE 2 DataRequest

UE 3 dataRequest

UE 4 DataRequest

UE 5 DataRequest

UE 6 Data

Request

NodeB PacketScheduler

Round Robin Scheduler

NodeB Buffers

Proportional Fair Resource Scheduler


39/124


Proportional Fair Resource Scheduler

CQIinformation

UE1

3

CQIinformation

UE3

2

1

Increases system throughput byserving the user above theiraverage data rate requested

Advantage:

Higher throughput than roundrobin

Disadvantage:Very complex to design

Scheduler calculates possibledata rate according to CQI

reports

Moving average for each usercalculated over a period of time.Check historyallocate credits

Combine with MA

UE1PDR1MA1

UE2PDR2MA2

UE3PDR3MA3

Compute new data rate

User with best ratio isscheduled first

Method of Operation

Module 2 Air Interface


40/124


Module 2 Air Interface

Explain the effect of power on HSDPA overall

Explain the relationship between the parameters PtxTargetHSDPA andPtxOffsetHSDPA

Explain HSDPA priority

Explain the initial bit rate for the HSDPA uplink

Explain HSDPA connection release

Explain SHO parameters in HSDPA


The HSDPA Air Interface


41/124


The HSDPA Air Interface

In RAS05 the air interface does not have any direct impact on the

dimensioning of the network elements

The air interface parameters will however have an impact on how

the end user will experience the HSDPA service

There is no recommended set of parameters that should be used

HSDPA Features in: RAS05 (RN2.1)


42/124


RRM

HSDPA Associated Uplink DPCHScheduling

64, 128 or 384 kbit/s uplink

.

HSDPA Channel Switching

HSDPA Mobility Handling with DCHSwitching

HSDPA Physical Channel, TransportChannel and Radio Bearer Configuration

HSDPA Resource Allocation

HSDPA with Additional RAB Initiation

Telecom Basic HSDPA with QPSK and 5 Codes

1 HS-SCCH, 5 HS-PDSCHs.

16 HSDPA users / NodeB.

1 HSDPA WSPC / NodeB.

3 HSDPA cells / NodeB.

Encoding, decoding.

Link Adaptation.

HARQ, Incremental Redundancy.

Data rates up to 1.8 Mbit/s

HSDPA NodeB Packet Scheduler

HSDPA Flow Control

HSDPA RRC State Handling

HSDPA Shared Control Channel PowerControl

HSDPA Features in: RAS05 (RN2.1)

Transport

HSDPA Transport with Best Effort AAL2QoS

Operability HSDPA Local Management for PM

RNC Site

RNC HSDPA Node B Connectivity (288NodeBs)

Directed RRC Connection Setup for HSDPA:

RAN964


43/124


RAN964

HSDPA Enabled CellSector ID = 1

non-HSDPA enabled CellSector ID = 1

R5 MobileHSDPA capable

Connection request

1

Mobile is R5 mobileSupports HSDPAResources are available.Call type is IA/BG service class.Re-direct to HSDPA layer.

2

Mobile is R99/R4 mobile.Does not support HSDPAResources are available.Re-direct to non-HSDPA layer.

4

R99/R4 Mobilenon HSDPA

3

Connection request

HSDPA Flow Control: RAN871


44/124


NodeB algorithm calculates flow control credits and feeds back buffer status to the RNC

NodeB flow controlmonitors theNodeB buffers and

measures the UEthroughput for eachqueue

Sc

heduler

Packet

111011

000001

010010

101001

001111

111011000011

101111

001110

011001

101110

101010

110011

010101

BTS Buffers

User datafrom RNC

RNC

HSDPA Local Performance Management: RAN870
http://localhost/var/www/apps/conversion/tmp/scratch_4//NCSBSR24OU/MKOIVULU$/Ty%C3%B6t/T%C3%B6it%C3%A4&versioita/DirectCost/NORA_directcost_copy010600.xls


45/124


g

The practical performance of the HSDPA solution can bemonitored

Achieved using RNC and BTS element managers

HSDPA performance indicator data collected in the RNC andNodeB

HSDPA performance indicator data collected in the RNC canbe reported to NetAct

NetAct support for HSDPA will be implemented on top of OSS4with a change delivery

HSDPA Packet schedulerRound Robin: RAN869


46/124


UE 1

UE 6

UE 5

UE 4

UE3

UE 2

UE 1 Data

UE 2 Data

UE 3 data

UE 4 Data

UE 5 Data

UE 6 Data

NodeB PacketScheduler

NodeB Buffers

UE 1

UE 2UE 3

UE 4

UE 5

UE 6

WBTS Sector 1

WBTS Sector 3WBTSSector 2

HSDPA Physical Channel, Transport Channel and

Radio Bearer Configuration: RAN822


47/124


Radio Bearer Configuration: RAN822

Physical and Transport Channels have several parameters that need to be

configured

Done on the fly by the system

Parameters are received from the RNC

The NodeB sets the radio parameters to correspond to the supported UE

categories

The parameters signalled to the UE using the RRC signalling and to theNodeB using NBAP signalling (3GPP defined)

Most of the parameters are static in all cells of the network e.g. Number of

HARQ processes, Ack/Nack parameters, CQI values etc.

Parameters such as HS-SCCH code are cell specific and implemented with

recommended default values The operator cannot adjust these parameters

HSDPA Resource Allocation: RAN821 1/3


48/124


The code and power resources to be used for HSDPA are allocated to theNodeB by the RNC

HSDPA power allocationcell specific (WCEL) parameters HS-PDSCH codes (SF 16 is used; RAS05 code use fixed to 5)

HS-SCCH code (RAS05 is fixed to 1)

Operators can define a separate power level threshold below which HSDPAcan be allocated

Operators can define a separate power level threshold above which HSDPAresources should be released

HSDPA can be allocated a priority higher or lower than NRT on the DCH

New counters for the HSDPA power levels in each WCELL

New alarms BTS WSPC for HSDPA is out of use and RNC DMPG for

HSDPA is out of use when the HSDPA service related to the BTS HSDPA orRNC HSDPA processing capacity is out of use



49/124


Max power

Ptx_offset_HSDPA

Ptx_target_HSDPA

A B

Node-B Tx power

PtxnonHSDPA

PtxNC

Ptxtotal

Ptx_target

C

HSDPAPriority = 1HSDPA has priority

Over DCHs

PtxNC PtxTarget HSDPA

PtxNonHSDPA PtxTarget HSDPA + PtxOffsetHSDPA

PtxNonHSDPA PtxTargetHSDPA + PtxOffsetHSDPA

PtxMaxHSDPA



50/124


A B

Max power

Node-B Tx power

Ptx_offset_HSDPA

PtxnonHSDPA

PtxNC

Ptx_target_HSDPA

Ptxtotal

Ptx_target

C

Ptx_offset

HSDPAPriority = 2DCHs have priority

Over HSDPA

PtxTotal PtxTarget HSDPA

PtxMaxHSDPA

PtxNonHSDPA PtxTarget HSDPA + PtxOffsetHSDPA PtxNonHSDPA PtxTarget + PtxOffset

HSDPA with Additional RAB Initiation: RAN820


51/124


HSDPA is suspended whenanother RAB setup is

initiated (e.g. Video call) Multicall combinations on

dedicated channels can beused

bit rate

time

HS-DSCHDCH

VIDEO CALL ON DCH

After HSDPA is suspended,DCH packet schedulingprocedures can be applied -> ifthere is still enough data in thebuffer a DCH is allocated

Video call is initiated ->

HSDPA is suspended

HSDPA Shared Control Channel Power Control:

RAN766


52/124


RAN766

The HS-SCCH power is adjusted according to the power levelrequired at the UE

The HS-SCCH power is adjusted every TTI

This is based on the Ack/Nack/DTXs received from the UE onthe UL HS-DPCCH

This reduces the average power overhead

Increases cell throughput gain by between 5 and 20% due topower not being wasted by transmitting a fixed power level

The HS-SCCH power levels in each WCELL can be followedup through new counters

Basic HSDPA with QPSK and 5 Codes: RAN763


53/124


Provides the basic HSDPA functionality

Allows 1.8 Mbps DL data rate over the air interface using QPSK modulation Maximum number of 16 HSDPA users per NodeB

Maximum number of 5 HSDPA codes per user (SF16,11 to SF16,15 )

Maximum number of 5 HS-PDSCH codes per cell (SF16)

Maximum number of 1 HS-SCCH codes per cell (SF128)

3 cells per NodeB can be enabled for HSDPA

RNCDMCU/DMPG pooling NodeBWSP-C

New counters for the number of QPSK capable UEs per WCELL

New alarm for HSDPA physical channel reconfiguration failures when theHSDPA service related to air interface is out of use

HSDPA RRC State Handling: RAN246


54/124


Necessary to enable state transitions from Cell_DCH to Cell_FACH state for

HSDPA users

Feature provides efficient radio and DSP resource usage in the RAN

Helps to conserves UE battery power

HSDPA resources are more efficiently utilised as inactive HSDPA users are

moved out of Cell_DCH state so that other users can use the resources

Timers and triggers to move the HSDPA users from Cell_DCH to Cell_PCHdue to DL/UL inactivity or utilisation status are available to the operators.

Please see addendum RNC, WBTS, WCEL Parameters Related to HSDPA

HSDPA Channel Switching: RAN235 2/2


55/124


Determines whether a user in a cell is allocated to a HS-DSCH or not

based on

UE capabilityCell resource availabilityUE handover statusUE multi-RAB configuration

User inactivity determines how long to keep the HS-DSCH reserved for aspecific user

Specific priority classes can be configured for NRT interactive so thatHSDPA will not be used.

Whether background class will be allocated HSDPA or not can be definedseparately

HS-DSCH setup requests and setup success vs. failures can be followedup through new RAN Level KPIs and counters.

HSDPA Channel Switching: RAN235 1/2


56/124


PS channel typedownlink selection

Selectionbetween FACH

andDCH or HS-DSCH

Selectionbetween DCH

HS-DSCH

Data transferusing FACH

Data transferusing DCH

Data transferusing HS-DSCH

HSDPA Associated Uplink DPCH Scheduling:

RAN233


57/124


HS-DSCH up to 1.8 Mbps (DL)

DCH 64, 128 or 384 Kbps (UL)

HSDPAinitialBitrateULInitial bit rate that will be allocated.

HSDPAminAllowedBitrateULMin allowed bitrate when

the bit rate is downgraded. Must be equal to or smaller thanHSDPAinitialBitrateUL

HSDPA Mobility Handling with DCH Switching:

RAN230


58/124


RAN230

Scheduled datacontinues todownload usingDCH X/Y. Scheduleddata ends DCHdropped. Newcapacity request

Active set=1allocate HS-DSCH

SHO RegionHS-DSCHService Area HS-DSCHService Area

UE is allocated DCH 0/0.A capacity request isreceived and DCHX/Y isallocated to supportdata transfer

Data scheduled toUE. Active set=1 soUser can be allocatedHS-DSCH. Active set>1implement mobility

procedure and HO toDCH 0/0

HSDPA Mobility Handling with DCH Switching:RAN230


59/124


Data scheduled toUE. Active set=1 canbe allocated HS-DSCH.

Active set>1implement mobilityprocedure and HO toDCH 0/0

Cell_DCH 0/0

Cell_DCH X/Y

Capacity_request

SHO RegionHS-DSCH

Service Area

HS-DSCH

Service Area

Cell_FACH/PCH

low/no data rate

AllocateHS-DSCH

Active Set =1

Capacity_request

Mobility improvements in RAS05


60/124


Change in RAS05 E5/pilot software

Available in pilot CD 3.0 (most likely)

Change in channel switching due to event 1a:

New functionality

HS-DSCH => FACH =>HS-DSCH

Original functionality

HS-DSCH => DCH0/0 => DCH_initial_bitrate

RAS05 Mobility with DCH switchingRAS05 trial


61/124


Once the session is in DCH, it

remains there until the buffers

are empty. After that, HSDPA

can be selected

HS-DSCH coverage HS-DSCH coverage

Service in

HSDPA

Switching to

DCH within the

SHO area

Cell A Cell B

HSDPA

DCH

0

Throughput

128kbps or 384kbps according to settings

64kbps

Upgrade to

initial bitrate

(e.g. 64 kbps)

Time

Upgrade to 128

/ 384 kbps

RAS05 Mobility with DCH switching + Resumption

timer

RAS05+CD


62/124


HSDPA resumption timer

switches the user from DCH to

HS-DSCH, when UE exits SHO

area


Service in

HSDPA

Switch

to DCH

0/0

Cell A Cell B

HSDPA

DCH

0

Throughput

64kbps

128kbps or 384kbps according to settings

Upgrade

to e.g.

64 kbps

Upgrade

to 128 /

384 kbpsSwitch

to HS-

DSCH

UE on

HS-

DSCH

Serving Cell Change via cell_FACHRAS05 E5/pilot


63/124


Serving Cell Change switches

the user from HS-DSCH to

Cell_FACH then back to HS-

DSCH


Service in

HSDPA

Switching to

Cell_FACH

within the SHO

area

UE on HS-

DSCH

Cell A Cell B

HSDPA

DCH

0

Throughput

64kbps

128kbps or 384kbps according to parameter settings

Details on Cell Change via cell-FACHRAS05 E5/pilot


64/124


The same parameter settings apply for this feature as for the DCH switching

no need for re-planning

HSDPA Serving Cell Change via Cell-FACH feature is used only in intrafrequency handover cases, in case of IFHO or ISHO the original DCH switching

procedures are used

If the user was moved to Cell-FACH because of intra frequency handover no

HSDPA user penalty timers are used on Cell-FACH, the user will be immediately

switched to a new HSDPA connection when there is a data volume request eitherfrom the UE or RNC

If the user was moved to Cell-FACH because of low utilization or low throughput

then the HSDPA user penalty timers are used on Cell-FACH

If the HSDPA user moves to non-HSDPA cell, the user in HO area will be moved

to Cell-FACH. The user will be immediately switched to the DCH of therequested bit rate when there is a data volume request either from the UE or

RNC (no need for first DCH 0x0DCH Initial bit rateDCH Final bit rate)

Measurement results


65/124


Initial mobility method New mobility proposal

1 Mbps

Conclusions


66/124


Improvement to HSDPA mobility in RAS05 greatly improves long download

performance on HSDPA

The benefits are significant even after HSDPA resumption timer, and even largerprior to that

Changing the cell via cell_FACH is faster than doing channel type switching to

DCH

Additionally with cell_FACH method, the user is back on HS-DSCH with good

download speeds With DCH switch method it takes time for the user to actually get e.g. 384 kbps,

and with resumption timer configuration to HS-DSCH cause a break again

New method would replace the existing DCH switching method as a mobility

solution in RAS05 E5

HS-DPA Mobility Handling with DCH Switching:RAN230


67/124


Separate parameters sets for HSDPA UE is implemented byincluding a HSDPA specific identifier in the WCEL parameters

The following object classes can be defined for each cell

Intra Frequency Measurement ControlFMCS

Inter Frequency Measurement ControlFMCI

Inter System Measurement ControlFMCG

Intra Frequency Handover PathHOPS

Fallbacks from the HS-DSCH to the DCH can be followed upthrough new counters

HSDPA Initial Up Link Bit Rate


68/124


This is set by the RNC parameter HSDPAinitialBitrateULand

defines the initial bit rate for the scheduling of the associated

UL DCH64Kbps (default value), 128Kbps or 384Kbps

Required to be equal to or greater than RNC parameter

HSDPAminAllowedBitrateUL.64Kbps (default) 128Kbps or

384Kbps

The bit rate is subject to normal DCH bit rate reschedulingaccording to current load and incoming RT connections

HSDPA Connection Release


69/124


L3 begins the release procedures to release the UL NRT DCHand MAC-d flow if:

The MAC-d flow is under utilised and the UL NRT DCH can be releasedas specified for other than HSDPA related UL NRT DCHs

The MAC-d flow has low throughput and the UL NRT DCH can bereleased as specified for other than HSDPA related UL NRT DCH. Theoperator configurable timer HsdschGuardTimerLowThroughputisstarted for this case

L2 inactivity supervision and the L3 inactivity timer are not usedfor the MAC-d flow. They are only used for NRT DCHs

SHO Parameters


70/124


Can be set differently for HSDPA

Smaller SHO areas can be used for UEs using the HS-DSCH No SHO for HS-SCCH

If the SHO area is smaller the UL DCH will need to use higher

power

Setting these parameters requires careful consideration

Module 3Effect of HSDPA Power on Throughput


71/124



Explain the effects of average cell throughput

Explain Bit Rate Distribution within a cell

Effect of Power on HSDPA Throughput, shared carrier


72/124


Bit Rate Distribution in a Cell


73/124


HSDPA Power


74/124


HSDPA power parameters are probably the single most

important parameters that need to be considered in the network

The power parameter settings will determine the average bit

rates that are available for the users

HSDPA Strategy

Probability of receiving HSDPA service can be controlled per cell


75/124


y g pwithPtxTargetHSDPA, PtxOffsetHSDPA and HSDPAPriority

PtxTargetHSDPA = high value close to PtxTarget, HSDPAPriority=1 - high availability for HSDPA users even if the DCH usage inthe cell is high

High HSDPA availability will mean lower service availability forR99 users especially NRT users.

These parameters should be very carefully considered beforedeciding on values

Module 4 - Setting HSDPA Parameters

C b t b d bit t i t


76/124


Can be set based on bit rate requirements

Requirements with one scheduler/NodeB lower than for one scheduler per cell

Alternative approach to setting HSDPA power is to evaluate the spare powerafter DCH usage

Low DCH usageHigh HSDPA power allocation

High DCH usageLower HSDPA power allocation

When HSDPA taken into use power control will increase DL transmission power

for DCH users to keep BLER in targets

Increase in DCH power must be considered when setting PtxTargetHSDPA and

PTXOffsetHSDPA to prevent power possibly being taken away from HSDPA

soon after allocation

Planning parameters in RAN05General HSDPAenabled

Enables/disables the use of the HSDPA in the cell.


77/124


ab es/d sab es t e use o t e S t e ce

MaxBitRateNRTMACdflow

Defines the maximum bit rate of the NRT MAC-d flow.

Default, 1664 kbps

Power allocation

HSDPAPriority

Defines priority between NRT DCHs and MAC-d flows.

PtxTargetHSDPA

Used instead of PtxTraget.

Default, 38.5 dBm

PtxOffsetHSDPA

Used instead of PtxOffset.

Default, 0.8 dB

PtxMaxHSDPA

Defines maximum HSDPA transmission power.

WinLCHSDPA

Defines window size used for averaging PtxnonHSDPA measurements in load control purposes.

Default, 5

Planning parameters in RAN05

MAC d flow utilization and throughput measurement


78/124


MAC-d flow utilization and throughput measurement

MACdflowutilRelThr

Defines the low utilization threshold of the throughput measurement of the MAC-d flow.

Default 256 bps.

MACdflowutilTimetoTrigger

Defines the low utilization time to trigger timer

Default, 0s.

MACdflowthrouhgputRelThr

Defines the low throughput threshold of the throughput measurement of the MAC-d flow.

Default 0 bps.

MACdflowthroughputTimetoTrigger

Defines the low throughput time to trigger timer

Default, 5s

MACdflowthroughputAveWin

Defines the averaging window size of the MAC-d throughput measurement.

HsdschGuardTimeLowThroughput

Defines time when HS-DSCH allocation is not allowed for a UE, after the MAC-d flow is realease due to

low throughput.


Mobility control


79/124


Mobility control

HSDPAFMCS/I/Gidentifier

Identifies parameter set for inter-/intra-frequency and inter-system measurements of a user having HS-

DSCH allocated.

HSDPAHOPSidentifier

Identifies parameter set for intra-frequency HOs of a user having HS-DSCH allocated.

HsdschGuardTimerHO

Defines time when HS-DSCH allocation is not allowed for a UE, after successful channel type switching

to DCH due to any HO reasons.

Default, 5s.

HSDPARRCdiversity

Enables/disables diversity HO of the stand-alone signalling link after successful RRC connection setup

for the HSDPA capable UE.

(In RAN05, max. active set size is 1 and HS-DSCH serving cell change is not supported.

SHO and HO parameters effects only on triggering of channel type switching to DCH 0/0

kbps.)


UL return channel


80/124


UL return channel

HSDPAinitialBitrateUL

Defines the initial bit rate for scheduling of the HSDPA associated UL DCH.

Default, 64

HSDPAminAllowedBitrateUL

Defines the minimum allowed bit rate in UL that can be allocated by the PS to the HSDPA associated UL

DCH when downgrading bit rate.

Module 5Node B



81/124



Explain the BTS structure for HSDPA

Explain the requirements and how to enable HSDPA on a BTS

Explain HSDPA and the WSPC card

Explain dimensioning of the WSPC cards

Explain the WSP card types and their support of Common Channels

NodeB Structure

WAFR-busRR-bus

ST-busSR-bus

Carrier


82/124


R-bus

DSC-BUS

Iub

WAF

WTR WSM

WPA

WSP

WSP

WSP

DSC-BUS

WAF

WTR WSM

WPA

WS

P

WSP

WSP

DSC-BUS

WAF

WTR WSM

WPA

WSP

WSP

T-bus

RT-bus

WSP

WSP-Cassigned forHSDPA use.handles L1,

MAC-hs and FP

IFUIFU

AXU

IFU

WSC

CarrierInterFace

WAM

WAM

WAM

R-bus

WAM unithandles Control

and AAL2functions

Requirements to Enable HSDPA on a NodeB

WN3.0 Software installed on the NodeB


83/124


At least one WSP-C need to be installed in the NodeB to support

HSDPA using 5 codes A software update for the WSP-C is required to support HSDPA

No changes are required to any other units for HSDPA to betaken into operation and their dimensioning can be doneaccording to the normal guidelines

All types of WSP units can be combined in one cabinet

All NodeB types that can support the WSP-C unit will be able tosupport HSDPA

WSPC Allocation

HSDPA t t d b WSPA

WSPC Capacity

Without HSDPA:

HSDPA on an UltraSite WCDMA BTS Platform


84/124


HSDPA not supported by WSPA,

WSPD or WSPE units.

When HSDPA is enabled in a cell, theWSPC unit is allocated dynamically.

All HSDPA channels for a cell are

processed on the same WSPC.

The HSDPA WSPC can also handle

DCHs for any cell but with reduced

capacity.

The HSDPA WSPC can also handle

common channels, but that will further

reduce DCH capacity.

RAS05: One to three HSDPA cells

supported on one WSPC, capacity isshared between the cells within the

WSPC.

RAS05.1: HSDPA WSPC either per

BTS or per cell.

Without HSDPA:

64 DCHs at 16 kbit/s OR

48 DCHs + common channels

HSDPA 5 codes:

1.8/3.6 Mbit HSDPA downlink

(5 HS-PDSCH codes) AND

16 uplink HS-DPCCHs AND

30 DCHs at 16 kbit/s or

14 DCHs + common channels

Associated DCHs for the HSDPA

users will consume DCH capacity.

The WSP Channel Element and Common Channels

WSP Type CEs Bearer (Kbps) CEs required


85/124


WSPA 32

WSPC 64WSPD 32

WSPE 16

AMR voice 1

16 132 2

64 4

128 4

384 16

WSP

Type

Cells CEs required

for CCHs

WSPA 8 per cell

WSPC 1 - 3 16

WSPD CEs not

reduced for

CCHs

WSPE CEs not

reduced for

CCHs

If all types of WSP units were installed in the sameNodeB the CCH allocation would follow thispriority:

1) All CCHs to WSPA

2) WSPC if WSPA fully loaded or does not exist

3) WSPD if WSPA/C fully loaded or does not exist4) WSPE if WSPA/C/D fully loaded or does notexist

The WSP-C Unit and HSDPA

Processing power on the WSP = Channel Elements


86/124


Processing power on the WSP Channel Elements

32 CEs reserved from one WSP-C are required to handle the 5

code HSDPA implementation (HS-DSCH, HS-SCCH and HS-

DPCCH)

Reservation of the CEs for HSDPA is static and made at NodeB

start up if the flag is set (HSDPAenabled=1)

1 to 3 cells are supportedFor RAS05, 1 WSP-C will supportHSDPA for the whole NodeB

The associated channels are distributed across all the available

WSP cards in the NodeB regardless of association to WAM.

The CEs used for the associated channel must be on the sameWSP card

Baseband Capacity with 5 Code HSDPA (RAS05)Site

Configuration

HSDPA active

No HSDPA users

HSDPA active

HSDPA with UL 64or

128Kbps

HSDPAactive

HSDPA with UL 384Kbps
http://c/USERS/RN2.1-RAN05%20INFORMATION/HSDPA%20Theory%20Course/Orange%20UK%20Material/Example%20Baseband%20Calculations.ppt


87/124


An UL DCH at 64/128Kbps requires 4 CEs from the WSPunit

An UL DCH at 384Kbps requires 16 CEs from the WSP unit

This UL DCH is not the HS-DPCCH

Max. AMR users 128Kbps

+ max AMR users

+ max AMR users

Omni directional1 WSPC

64(32+16)=16 4 HSDPA + 0 AMR 1 HSDPA + 0 AMR

Omni directional

1 WSPC + 1 WSPA

(64+32) - (32+8)=56 14 HSDPA + 0 AMR 3 HSDPA + 8 AMR

Sectorised 1+1+1

1 WSPC

64 - (32+16)=16 4 HSDPA + 0 AMR 1 HSDPA + 0 AMR

Sectorised 1+1+12 WSPC

64*2-(32+16)=80 16 HSDPA + 16 AMR 5 HSDPA + 0 AMR

1+1+1

3 WSPC

64*3-(32+16)=144 16 HSDPA + 80 AMR 9 HSDPA + 0 AMR

Sectorised 1+1+1

2 WSPA + 1 WSPC

(32x2)+64-(32+24)=72 16 HSDPA + 8 AMR 4 HSDPA + 8 AMR

Example Baseband Calculations 1

Refer to slides WSP Channel Elements and common channelsand baseband Capacity with 5 Code HSDPA (RAS05)


88/124


p y ( )

Omni directional 1 WSPC

WSPC has 64 CEs32 CEs for HSDPA -16 CEs for CCHS = 16 CEs left for associated and AMR channelsUsing associated channel 16/128 for HSDPA requires 4 CEs from same WSP

16/4 = 4 rem 0

so support for 4 HSDPA users + 0 AMR users

Using associated channel 384 requires 16 CEs from same WSP16/16 =1 rem 0

so support for 1 HSDPA users and 0 AMR users

Omni directional 1 WSPC + 1 WSPAWSPC has 64 CEs32 CEs for HSDPA = 32 CEs left for associated and AMR channelsWSPA has 32 CEs. According to rule CCHs should be assigned from WSPA and 8 CES required/cell for CCHs so 328 = 24 leffor use by associated channels and AMR channels

Using associated channel of 64/128 for HSDPA requires 4 CEs from same WSP

WSPC = 32/4 = 8 r 0 WSPA = 24/4 = 6 r 0

8 + 6 = 14

so support for 14 HSDPA users and 0 AMRusers

Using associated channel 384 requires 16 CEs from same WSPWSPA = 24/16 = 1 r 8 WSPC = 32/16 = 2 r 0

1 + 2 = 3 and 8 remaining

So support for 3 HSDPA users and 8 AMR users

Example Baseband Calculations 2

Sectorised 1 + 1+ 1 with 1 WSPC


89/124


WSPC has 64 CEs32 CEs for HSDPA -16 CEs for CCHS = 16 CEs left for use by associated channels and AMR channels

Using associated channel 16/128 for HSDPA requires 4 CEs from same WSP

16/4 = 4 rem 0

so support for 4 HSDPA users + 0 AMR users

Using associated channel 384 requires 16 CEs from same WSP

16/16 =1 rem 0

so support for 1 HSDPA user and 0 AMR users

Sectorised 1 + 1+ 1 with 2 WSPCWSPC 1has 64 CEs - 32CEs for HSDPA16 CEs for CCH s= 16 CEs left for use by associated channels and AMR channelsWSPC 2 has 64 CEs by associated channels and AMR channels


WSPC 1 = 16/4 = 4 r 0 WSPC 2 = 64/4 = 16 r 0

RAS05 only supports 16 HSDPA users/NodeB(WSPC 2 fulfills this) and therefore all remaining WSPC 1 CEs must be used for

AMR



WSPC 1 = 16/16 = 1 r 0 WSPC 2 = 64/16 = 4


Example Baseband Calculations 3 Sectorised 1 + 1+ 1 with 3 WSPC

WSPC 1has 64 CEs - 32CEs for HSDPA16 CEs for CCHs = 16 CEs left for use by associated channels and AMRchannels


90/124


WSPC 2 has 64 CEs left for use by associated channels and AMR channels

WSPC 3 has 64 CEs left for use by associated channels and AMR channels

Using associated channel of 64/128 for HSDPA requires 4 CEs from same WSPWSPC 1 = 16/4 = 4 r 0 WSPC 2 = 64/4 = 16 r 0 WSPC 3 = 64/4 = 16 r 0

RAS05 only supports 16 HSDPA users/NodeB(WSPC 2 fulfills this) and therefore WSPC 1 and WSPC 3 CEs must beused for AMR

WSPC 1 = 16 CEs and WSPC 3 = 64 CEs = 80 CEs

so support for 16 HSDPA users 80 AMR users


WSPC 1 = 16/16 = 1 r 0 WSPC 2 = 64/16 = 4 r 0 WSPC 3 = 64/16 = 4 r 0


Sectorised 1 + 1+ 1 with 2 WSPA and 1 WSPCWSPC 1 has 64 CEs32 CEs for HSDPA = 32 CEs left for use by associated channels and AMR channels

WSPA 1 has 32 CEs(3 X 8 CEs for CCHs) = 8 CEs left for use by associated channels and AMR channels

WSPA 2 has 32 CEs left for use by associated channels and AMR channels


WSPA 1 = 8/4 = 2 r 0 WSPA 2 = 32/4 = 8 r 0 WSPC = 32/4 = 8 r 0

RAS05 only supports 16 HSDPA users/NodeBand therefore all WSPA 1 CEs can be used for AMR

so support for 8 + 8 = 16 HSDPA users + 8 AMR users

Using associated channel 384 requires 16 CEs from same WSPWSPA 1 = 8/16 = 0 r 8 WSPA 2 = 32/16 = 2r 0 WSPC = 32/16 = 2 r 0

so support for 2 + 2 = 4 HSDPA users and 8 AMR users

RAS05 HSDPA NodeB Configuration

3 HSDPA capable cells per NodeB


91/124


4 users

4 users8 users

16 HSDPA users per NodeBcan be

distributed randomly between all

HSDPA capable cells

1 WSPC to support 3 HSDPA cells

HSDPAenabled parameter set in WCEL

Enabling HSDPA on a Node B

WN3.0 software installed in the NodeB
http://localhost/var/www/apps/conversion/tmp/scratch_4//NCSBSR24OU/MKOIVULU$/Ty%C3%B6t/T%C3%B6it%C3%A4&versioita/DirectCost/NORA_directcost_copy010600.xls


92/124


RN2.1 software installed in the RNC

DMPGs allocated to the HSDPA pool

HSDPAenabled parameter set on (WCELL)

At least one WSPC card to be dedicated to HSDPA

functionality

The Nokia OSS system will require OSS4 software and a CD

delivery on top of the OSS4 software

Module 6IUB



93/124


Explain the new Iub over ATM solution

Explain dimensioning for Iub capacity Explain Iub parameters SHAS and SHFCAS

ATM over the Iub

RAS05 offers a new Iub solution allowing high capacity data to


94/124


be carried efficiently

Iub bandwidth is divided between signalling links on AAL5,O&M on AAL5 and UP VCCs on AAL2

User plane VCCs transport CCHs, DCCHs and DTCHs

HSDPA improves Iub efficiency compared to Release99 packet datasince HSDPA is a time shared channel with flow control in Iub

R l 99 i d di t d f th RNC t th UE

Iub Efficiency with HSDPA


95/124


Release99 requires dedicated resources from the RNC to the UE.Those resources are not fully utilized during TCP slow start or during

inactivity timer periods HSDPA does not use soft handover no need for soft handover

overhead in Iub

= User 1

= User 2= User 3

E1 for BTS1

E1 for BTS2

E1 for BTS1

1 2

1 = TCP slow start

2 = Inactivity timer

3

3 = Soft handover for some connections

HSDPA improves the Iubefficiency by 50-70% dueto time multiplexing anddue to no soft handover

Algorithm runs on Node B. Operated

per priority queue.

RNC chooses when to send the data

during each interval.

Iub Flow Control


96/124


per priority queue.

Inputs:

Amount of data at Node B Estimated throughput

Outputs:

When to send Capacity Allocation

message?

Maximum MAC-d PDU size

HS-DSCH credits HS-DSCH interval

HS-DSCH repetition period

g

RNC may further limit the amount of

data to send based on Node B has allocated more capacity

than there is data to send.

Iub capacity is limiting (scheduling for

this at RNC).

Example

credits = 4

interval = 10 ms

repetition = 3

10 ms 10 ms 10 ms= MAC-d PDUmax 63 credits

Dimensioning the Iub Capacity

It is the Nokia recommendation that NetAct Transmission


97/124


Planner be used to dimension the Iub interface

The Iub dimensioning will not be affected much with theintroduction of HSDPA in RAS05 and the RAN04 dimensioning

will probably be adequate

Iub Parameters

The available Iub capacity is required to be shared between

HSDPA d DCH ffi

1/5


98/124


HSDPA and DCH traffic

There are two main parameters that affect this:

Shared HSDPA Allocation SizeWBTS

Shared HSDPA Flow Control Allocation SizeWBTS

Shared HSDPA AAL2 Allocation Size,

Shared HSDPA Flow Control Allocation Size

2/5


99/124


HSDPA only pipe

Shared pipe

Shared HSDPA AAL2 Allocation Size


DCH only pipe

HSDPA Transport with Best Effort AAL2 QoS:RAN236


100/124


HSDPA reservation = MaxDCH usage when a HSDPAuser is present

DCH only pipe

Shared pipeDCH has strictpriority

HSDPA only pipe

DCH Traffic

HSDPA Traffic

HSDPA maxoverbooking

Shared HSDPA AAL2 Allocation Size

WBTS Parameter

Mandatory creation parameter

3/5


101/124


SharedHSDPAallocation

Indicates the guaranteed bit rate in the Iub for HSDPA traffic

Reservation only made when the first HSDPA user enters the cell

The value of the parameter depends on the priority required for the HSDPA trafficifHSDPA traffic is not as important as DCH traffic then assign a low value

300Kbps is the recommended minimum size

1Mbps is the recommended size for a 1+1+1 site with only 1 WSPC

Range 0 to 7.2 Mbps in 0.1 Mbps steps


WBTS parameter

4/5


102/124


SharedHSDPAFlowControlAllocation

Indicates the maximum data rate the RNC may use to send mac-d data on the Iub

DCH traffic has strict priority except for the reserved capacity allocated by theSharedHSDPAallocation parameter

Initially this parameter could be set at 1.25 X average air interface throughput

Maximum value should be Total Iub capacity minus signalling traffic requirements

Too high DCH usage and aggressive setting will result in mac-d data buffering atAAL2 level

Module 7RNC


Explain RNC features associated with the RNC in RAS05


103/124


Explain RNC features associated with the RNC in RAS05

Explain the effects of HSDPA on traffic capacity in the RNC Explain RNC connectivity

Explain the concept of the HSDPA pool

Traffic Capacity

There is a suggested maximum limit on how much data the RNC can pass onto theIub depending on the traffic types

DCH PS 196Mbps


104/124


DCH PS 196Mbps

HSDPA 100Mbps DCH CS 196Mbps

AMR 12.2 6800 Erlang depending on the number of HSDPAenabled BTSs in the RNC

The values above are theoretical limits when no other traffic types are present

The following formula indicates the feasibility of all 4 traffic mixes

AMR + SHO x (DCH_CS + DCH_PS) + 1.4 x HSDPA < 1

6800 196Mbps

SHO = Soft Handover overheadNetwork dependant and typically 1.31.4

1.4 is a factor used to take into accountthe heavier processing load caused byHSDPA

RNC Connectivity (Feature RAN957)

RAS05 can support up to 384 NodeBs/1152 cells

HSDPA can only be enabled in 288 NodeBs/864 cells


105/124


DMPGs are reserved from the RNC DMCUs for the HSDPA poolthe amount

depends on the number of HSDPA users

The maximum number of DMPGs in the RNC configuration can be 48

Between 1 and 4 DMPGs can be allocated from each DMCU to HSDPA.

AMR traffic in the RNC is linearly dependant on the on the number of DMPGsoutside the HSDPA DMPG pool

Each full DMCU reserved for HSDPA traffic reduces the maximum AMR Erlangfigure (6800) by 155 Erlang => for each DMPG it will be 155/4 ~ 39 erlang

AAL2 connectivity limit for the RNC is 1000Mbps(1Gbps) and does not reflect thetotal amount of traffic but rather the physical connections

RN2.1 HSDPA DMPG Pooling Concept

HSDPA UEHSDPA DMPG Pool

HSDPA UEDMPG-0

DMPG 1


106/124


NodeB

HSDPA UE

non

HSDPA UE

Normal DMPGs

RNC

NodeB

HSDPA UE

non

HSDPA UE

DMPG-1

DMPG-2

DMPG-6

DMPG-3

DMPG-7

DMPG-8

DMPG-9

ANY QUESTIONS?
http://localhost/var/www/apps/conversion/tmp/scratch_4//NCSBSR24OU/MKOIVULU$/Ty%C3%B6t/T%C3%B6it%C3%A4&versioita/DirectCost/NORA_directcost_copy010600.xlshttp://localhost/var/www/apps/conversion/tmp/scratch_4//NCSBSR24OU/MKOIVULU$/Ty%C3%B6t/T%C3%B6it%C3%A4&versioita/DirectCost/NORA_directcost_copy010600.xls


107/124


THANK YOU ALL

FOR YOUR TIME.


108/124


Addendum

Summary of NodeB Units WAFWideband Antenna Filter. Combines and isolates Tx/Rx signals as well as

amplifies the received signals. Typically one per sector

WPAWideband Power Amplifier. Operating bandwidth of 20Mhz on any section of the60Mhz band


109/124


60Mhz band

WTR-BWCDMA transceiver unit. One WTR can serve two cells with 2way uplinkdiversity

WSM- Wideband Summing and Multiplexing unit. Sums the Tx signals from the signalprocessing units or other WSMs

WSPWideband Signal Processor. Performs Tx and Rx channel code processing,coding and decoding functions. Number of WSPs is determined according to the

expected NodeB traffic

WAMWideband Application manager. Performs O&M and carrier control functions. Upto six units can be installed in certain NodeBs and in this case 3 will act as primaryWAMs (slot 0) and the other 3 as secondary WAMs (slot 1). One primary WAM at a timeis selected as the master telecom and O&M unit by the system.Master WAM takes careof the NodeB cabinet level control functions.NodeB start up, temperature control,

configuration and O&M processing. All WAM units perform telecom control functions,logical resource management, ATM processing and transport channel frame protocolprocessing.

RNC Parameters Related to HSDPA Activation

MaxBitRateNRTMACdflow (Maximum bit rate of NRT MAC-d flow)

MACdflowutilRelThr (Low utilisation threshold of the MAC-d flow))

MACdflowthroughputAveWin (Averaging Window size of the MAC-d flow throughput


110/124


g p ( g g g pmeasurement)

MACdflowthroughputRelThr (Low throughput threshold of the MAC-d flow)

MACdflowutilTimetoTrigger (Low utilisation time to trigger of the MAC-d flow)

MACdflowthroughputTimetoTrigger (Low throughput time to trigger of the MAC-dflow)

HsdschGuardTimerLowThroughput (HS-DSCH guard timer due to low throughput)

HsdschGuardTimerHO (HS-DSCH guard time after switching to DCH due to HO)

HsdpaRRCdiversity (SHO prohibition for HSDPA-capable UE)

HSDSCHQoSclasses (HS-DSCH QoS classes)

HSDPAminAllowedBitrateUL (Minimum allowed bit rate in uplink for HSDPAassociated UL DCH)

HSDPAinitialBitrateUL (Initial bit rate in uplink for HSDPA associated UL DCH)

HSDPAPriority (HSDPA priority)

WBTS Parameters Related to HSDPA Activation

WinLCHSDPA (PtxnonHSDPA averaging window size for load control)

SharedHSDPAallocation (Shared HSDPA AAL2 allocation)

NbrOfO erbookedHSDPAUsers (N mber of o erbooked HSDPA sers)


111/124


NbrOfOverbookedHSDPAUsers (Number of overbooked HSDPA users)

ReleaseTimerForSharedHSDPAallocation (Release timer for shared HSDPAallocation)

SharedHSDPAVCCSelectionMethod (Shared HSDPA AAL2 VCC selection method)

SharedHSDPAFlowControlAllocation (Shared HSDPA flow control allocation)

WCEL Parameters Related to HSDPA Activation

HSDPAenabled (HSDPA enabled)

PtxTargetHSDPA (Target for transmitted non-HSDPA power)

PtxMaxHSDPA (PtxMaxHSDPA)


112/124


PtxMaxHSDPA (PtxMaxHSDPA)

HsdpaFmcsIdentifier (HSDPA FMCS identifier)

HsdpaFmciIdentifier (HSDPA FMCI identifier)

HsdpaFmcgIdentifier (HSDPA FMCG identifier)

PtxOffsetHSDPA (Offset for transmitted non-HSDPA power)

Parameter name: HSDPA enabled

Abbreviated name: HSDPAenabled

Management Parameters for HSDPA RRM 1/8

General Parameters


113/124


Range: Yes, No

Default: No

Object: WCEL

Parameter name: Maximum bit rate of NRT MAC-d flow

Abbreviated name: MaxBitRateNRTMACdflow

Range: 64, 128, 256, 384,512, , 14080,step 128 kbps

Default: 1664 kbps

Object: RNC

Mobility Control Parameters

Parameter name: HSDPA FMCS identifier

Abbreviated name: HSDPAFmcsIdentifier

Range: 1 100, step 1

Default: Not applicable

Object: WCEL


Parameter name: HSDPA FMCI identifier

Abbreviated name: HSDPAFmciIdentifier



114/124



Object: WCEL

Parameter name: HSDPA FMCG identifier

Abbreviated name: HSDPAFmcgIdentifier



Object: WCEL

Parameter name: HSDPA HOPS identifier

Abbreviated name: HSDPAHopsIdentifier



Object: ADJS


Parameter name: HS-DSCH guard time after channelt it hi d t HO


115/124


type switching due to HO reasons

Abbreviated name: HsdschGuardTimerHO

Range: 0 30 s, step 1

Default: 5 s

Object: RNC

Parameter name:

SHO prohibition after RRC connectionsetup for HSDPA capable UE

Abbreviated name: HSDPARRCdiversity

Range: 0 (SHO not allowed) 1 (SHOallowed), step 1

Default: 1

Object: RNC


Power Allocation Parameters

Parameter name: PtxTargetHSDPA

Abbreviated name: PtxTargetHSDPA


116/124


g

Range: -10 50 dBm, step 0.1

Default: 38.5 dBm

Object: WCEL

Parameter name: Ptx Max HSDPA

Abbreviated name: PtxMaxHSDPA

Range: 0 50 dBm, step 0.1

Default: 37.8 dBm

Object: WCEL

Parameter name:

HSDPA priority

Abbreviated name: HSDPAPriority

Range: 1 2, step 1

Default: 1

Object: RNC


Parameter name: PtxnonHSDPA averaging window size


117/124


Parameter name: PtxnonHSDPA averaging window sizefor LC

Abbreviated name: WinLCHSDPA

Range: 0 20, step 1

Default: 5

Object: WBTS

Parameter name: PtxOffsetHSDPA

Abbreviated name: PtxOffsetHSDPA

Range: 0 6 dB, step 0.1

Default: 0.8 dB

Object: WCEL

Management Parameters for HSDPA RRM 6/8MAC-d flow throughput measurement parameters

Parameter name: Low utilization threshold of the MAC-dflow

Abbreviated name: MACdflowutilRelThr

Range: 0 64000 bps step 256


118/124


Range: 0 64000 bps, step 256

Default: 256 bps

Object: RNC

Parameter name: Window size of the MAC-d flowthroughput measurement

Abbreviated name: MACdflowthroughputAveWin

Range: 0 10 s, step 0.5 s

Default: 3 s

Object: RNC

Parameter name: Low throughput threshold of the MAC-d flow

Abbreviated name: MACdflowthroughputRelThr

Range: 0 64000 bps, step 256

Default: 0

Object: RNC


Parameter name: Low utilization time to trigger of theMAC-d flow

Abbreviated name: MACdflowutilTimetoTrigger



119/124


Default: 0 s

Object: RNC

Parameter name: Low throughput time to trigger of theMAC-d flow

Abbreviated name: MACdflowthroughputTimetoTrigger


Default: 5 s

Object: RNC

Parameter name: HS-DSCH guard timer due to lowthroughput

Abbreviated name: HsdschGuardTimerLowThroughput

Range: 0 240 s, step 1

Default: 30 s

Object: RNC

Management Parameters for HSDPA RRM 8/8Parameter name: HS-DSCH QoS classes

Abbreviated name: HSDSCHQoSclasses

Range: 0-15, step 1

Default: 15

Object: RNC


120/124


Other parameters

Object: RNC

Parameter name: Minimum allowed bit rate in uplink forHSDPA associated UL DCH

Abbreviated name: HSDPAminAllowedBitrateUL

Range: 64, 128, 384 kbps

Default: 64 kbps

Object: RNC

Parameter name: Initial bit rate in uplink for HSDPAassociated UL DCH

Abbreviated name: HSDPAinitialBitrateUL

Range: 64, 128, 384 kbps

Default: 64 kpbs

Object: RNC

UE Categories

HSDPA

Category5 CodesModulation 15 Codes10 Codes

Transport

Block sizeInter-TTI


121/124


10

9

7/8

5/6

3/4

1/2

12

11

-

-

-

3.6 Mbps

1.8 Mbps

1.2 Mbps

1.8 Mbps

0.9 Mbps --36302QPSK only

--36301QPSK only

QPSK/16QAM

QPSK/16QAM

QPSK/16QAM

QPSK/16QAM

QPSK/16QAM

QPSK/16QAM

14.0 Mbps

10.1 Mbps

-

-

-

-

-279521

-202511

7.2 Mbps144111

-72981

-72982

-72983

Applicable to

RAS05

(QPSK

CQI Reporting from UE

UE measures channel quality of CPICH

and assumes that HS-PDSCH codes

will be transmitted with combined power

CQI TBS codes MD

(dB)1 137 1 QPSK 02 173 1 QPSK 03 233 1 QPSK 04 317 1 QPSK 05 377 1 QPSK 06 461 1 QPSK 07 650 2 QPSK 08 792 2 QPSK 09 931 2 QPSK 0


122/124


(

and 5 codes) PHS-PDSCH = PCPICH +G.

Measurement power offset G signalled

to Node B and UE by NBAP and RRC.

Table to the right (from 25.214) defines

CQI for UE categories 1 to 6. Based on

10% BLER.

Reference power adjustment D is used

to signal how much quality is better

than maximum TBS supported by UE.

9 931 2 QPSK 0

10 1262 3 QPSK 011 1483 3 QPSK 012 1742 3 QPSK 013 2279 4 QPSK 014 2583 4 QPSK 015 3319 5 QPSK 016 3565 5 16QAM 017 4189 5 16QAM 018 4664 5 16QAM 019 5287 5 16QAM 0

20 5887 5 16QAM 021 6554 5 16QAM 022 7168 5 16QAM 023 7168 5 16QAM -124 7168 5 16QAM -225 7168 5 16QAM -326 7168 5 16QAM -427 7168 5 16QAM -528 7168 5 16QAM -629 7168 5 16QAM -730 7168 5 16QAM -8

16QAM 16 Quadrature Amplitude Modulation

A/N Ack/Nack

AM Acknowledge Mode

AAL2 ATM Ad t ti L t 2

DPCH Dedicated Physical Channel

DSP Digital Signal Processor

DTCH Dedicated Traffic Channel

DTX Di ti T i i

Abbreviations (1)


123/124


AAL2 ATM Adaptation Layer type 2

Ack Acknowledgement

ARQ Automatic Repeat Request

AS Active Set

ASIC Application Specific Integrated Circuit

ATM Asynchronous Transfer Mode

BLER Block Error Rate

CCS Channelisation Code Set

CQI Channel Quality Information

CRNC Controlling RNC

DCCH Dedicated Control Channel

DCH Dedicated Channel

DPCCH Dedicated Physical Control Channel

DTX Discontinuous Transmission

F Flag

FBI Feedback Information

FC Flow Control

FP Frame Protocol

H-RNTI HS-DSCH Radio Network Temporary

Identifier

HARQ Hybrid Automatic Repeat RequestHS-DPCCH High Speed Dedicated Physical

Control

Channel

HS-DSCH High Speed Downlink Shared Channel

HS-PDSCH High Speed Physical Downlink Shared

Channel

HS-SCCH High Speed Shared Control Channel

HSDPA High Speed Downlink

Packet Access

I In phase

LA Link Adaptation

SID Size Index Identifier

SRNC Source RNC

TBS Transport Block Size

TM Transparent Mode

Abbreviations (2)


124/124


LA Link Adaptation

M Modulation

MAC Medium Access Control

Nack Negative Acknowledgement

NDI New Data Indicator

PDU Protocol Data Unit

PHY Physical (Layer)

Q QuadratureQPSK Quadrature Phase Shift Keying

RLC Radio Link Control

RNC Radio Network Controller

RV Redundancy Version

SDU Service Data Unit

TM Transparent Mode

TNL Transport Network Layer

TPC Transmit Power Control

TSN Transmission Sequence Number

TTI Transmission Time Interval

UE User Equipment

UM Unacknowledged Mode

VF Version Flag

WAMA Wideband Application Manager

version A

WSPA Wideband Signal Processor version A

WSPC Wideband Signal Processor version C

WSPD Wideband Signal Processor version D

Documents

2_HSDPA Theory Course Vers4