Flexi 1Gb BB - Part 4 HSUPA Aspects 4

8/13/2019 Flexi 1Gb BB - Part 4 HSUPA Aspects 4

1/36

1 Nokia Siemens Networks 2012

For internal use

MBB CS Network Engineering / Krzysztof Mertas / Bartosz Wrobel

Network Engineering Training Session onFlexi 1GB Baseband Step by StepPart 4: HSUPA allocation, dimensioning & licensing

CS Voice dimensioningMulti RAB dimensioning (HSPA + AMR call)

19.09.2012

Bartosz Wrbel

Network Engineering


2/36


For internal use


General Information

This slide set shall notbe considered as an official feature description nor HSPA

performance document. All references to those details in this document are for

your convenience only and shall be double-checked from respective customer

documents before any quotations.

This document is not a RAN Dimensioning Guide. All capacity values

and performance figures in this document shall be verified from WCDMA

RAN documentation.


3/36


For internal use


Where to find more information about BasebandDimensioning ?

RU30 Baseband Dimensioning internal guideline

RAN_Dim Dimensioning tool

FAQ
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/424107386https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/318048181https://workspaces.emea.nsn-net.net/sites/NetworkEngineering/Lists/Discussions/AllItems.aspxhttps://workspaces.emea.nsn-net.net/sites/NetworkEngineering/Lists/Discussions/AllItems.aspxhttps://sharenet-ims.inside.nokiasiemensnetworks.com/Open/318048181https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/424107386


4/36


For internal use


Contents

General Introduction

RU30 Licensing aspects

RU30 Baseband dimensioning rules

Technical Details

Flexi System Module rel.2

Local Cell Grouping

HSDPA Dimensioning

HSDPA BTS Processing Set resources allocation

HSUPA Dimensioning

HSUPA BTS Processing Set resources allocation

R99 Dimensioning

Common Control Channels Dimensioning

Network Parameters

CS Voice Over HSPA Dimensioning

Multi RAB dimensioning


5/36


For internal use


Impact of RAN2123 on BTS dimensioning

New dimensioning

rulesNew baseband dimensioning

rules for System Module rel.2RAN21231 Gigabit Baseband

New licensing

aspectsNew licensing aspects

for System Module rel.2


6/36


For internal use



RAN21231 Gigabit Baseband

New licensing

aspectsNew licensing aspects

for System Module rel.2

New license for HSPA

New licenses describes HSPA performance (throughput and users)

HSDPA/HSUPA schedulers do not consume CE licenses any more.

Same approach for CE licenses

CE licenses are called now Rel99 CE licenses

R99 users consumes Rel99 CE licenses depending on bearer rate


7/367 Nokia Siemens Networks 2012

For internal use



New dimensioning

rulesNew baseband dimensioningrules for System Module rel.2

RAN21231 Gigabit Baseband Processing capability of System Module Rel.2 is significantly

increased comparing to RU10/RU20

Common Control Channels dimensioning is similar as in RU10/RU20Basic configurations (e.g. 3cells/20km or 6cells/10km) are supported with baseband

resources included in System Module Rel.2 capacity

48 Rel99 CE licenses are required per each step

R99 dimensioning same as in RU20 On Top

HSPA dimensioning approach changeNew baseband dimensioning rules, HSPA thr., number of users improvement



For internal use


HSUPA Dimensioning



For internal use


HW in RU30Flexi WCDMA BTS (1/2)System Module Rel.2 capacityHSUPA activated

HSUPA activation does not consume any baseband resources*.

However for HSUPA users and throughput processing baseband resources (subunits) needs tobe allocated based on current traffic need.

HSUPA baseband resources allocation is performed in stepsso called HSUPA resourcesteps. One step is equal to of System Module rel.2 subunit.

HSUPA baseband capacity reservation is based on HSUPA license (HSUPA BTS processing

sets)

In case if R99 CE licensed baseband resources are overlapping HSUPA licensed basebandresourcesoverlapped resources can be dynamically exchanged between R99 and HSUPA

users

One HSUPA BTS processing set license corresponds to 6HSUPA resource steps (1,5 subunit)(RU30EP1/EP2)

One HSUPA processing set does not correspond to 1 Subunit (RU30EP2) (see details onfurther slides)



For internal use


HW in RU30Flexi WCDMA BTS (2/2)Interference cancellation units

In case when Interference Cancellation feature is activated, Interference Cancellation units

(PIC pool) needs to be commissioned in order to perform interference cancellation formapped HSPA cells.

One PIC pool requires one subunit. Number of PIC pool is commissioned by operator

One PIC supports up to 6 cells (interference cancellation can be done simultaneously in 3selected by BTS cells)

Cells from one frequency layer should be mapped to one PIC pool

One PIC pool supports up to 2 frequency layers

Note that HSUPA scheduler cooperates only with PIC pools located in the same SystemModule

With 4 way Rx diversity feature single PIC pool supports up to 3 cells (interferencecancellation can be done simultaneously in 1 cell selected by BTS)



For internal use


HSUPA baseband resources allocation in RU30HSUPA Processing Set in RU30EP1 and RU30EP2

HSUPA license is called HSUPA BTS Processing Set

The HSUPA BTS Processing Set is a HSUPA BB resources reservation inside the Flexi System Module

Rel.2, that allows for a certain number of HSUPA users and HSUPA throughput.

HSUPA baseband resources allocation is performed in stepsso called HSUPA resource steps. One

step is equal to of subunit.

1 HSUPA Processing Set corresponds to 1,5subunit

1 HSUPA Processing Set allows to reach 5.8Mbps or 24 users

HSDPA thr.,

users, HSDPA

cells

HSDPA thr.,users, HSDPA

cells

HSUPA

licensed

capacity

HSUPAlicensed

capacity

HSUPA thr.,

usersHSUPA thr.,

users

HSUPA BTS

Processing set licenses

HSUPA BTS

Processing set

Unlicensed BB

capacity

HSUPA licensedcapacity

Users/throughput



For internal use


HSUPA baseband resources allocation in RU30SRB processing

HSUPA

Scheduler

(subunits)

UL

In RU30 with System Module rel.2 HSUPA does not consume any Rel99 CE licenses

HSUPA

Scheduler

(subunits)

No-FDPCH capable

UE or

F-DPCH capable UE

(rel.7) but F-DPCH

feature not activated

FDPCH capable UE

(rel.7) and F-DPCH

feature activated

SRB

(1CE UL)

SRB

(1CE DL)DL

UL

DL

RU30 brings SRB

processing

improvement (no

additional 1 CE

(UL/DL) for HSUPA

user (UL:HSUPAbearer, DL:HSDPA

bearer)

Less baseband resources needed for HSUPA

Rel99 CE licenses are not needed for HSUPA



For internal use


HSUPA in RU30 EP12 HSUPA schedulers per one LCG

In RU30EP1 with System Module Rel.2, one HSUPA scheduler can support up to 200HSUPA users

from 1 to 12 cells.

Up to one HSUPA scheduler is allocated per single LCG with single System Module Rel.2

Up to two HSUPA schedulers are allocated per single LCG with two System Modules rel.2 and

frequency layers mapping to HW (note that frequency mapping to HW is possible only in one

LCG scenario (RU30EP1/EP2))

up to 400 HSUPA users supported per LCG (2 x System Module rel.2)

LCG1

f1

f2

400 HSUPA

users per LCG200 HSUPA

users per

Extension

System Module

200 HSUPA

users per

Master System

Module


14/36


For internal use


HSUPA in RU30 EP22 HSUPA schedulers per one LCG

In RU30EP2 with System Module Rel.2, one HSUPA scheduler can support up to 240HSUPA users

from 1 to 12 cells

Up to one HSUPA scheduler is allocated per single LCG with single System Module Rel.2

Up to two HSUPA schedulers are allocated per single LCG with two System Modules rel.2 and

frequency layers mapping to HW (note that frequency mapping to HW is possible only in one

LCG scenario (RU30EP1/EP2))

up to 480 HSUPA users supported per LCG (2 x System Module rel.2)

LCG1

f1

f2

480 HSUPA

users per LCG240 HSUPA

users per

Extension

System Module

240 HSUPA

users per

Master System

Module


15/36


16/36


For internal use


BaseBand resources allocationNon- Overlapping baseband resources

Rel99 CE licensesHSDPA

commissioned

throughput

System Module Rel.2

Free (unlicensed) baseband

resourcesnot available for

R99 users and HSPA data

users

License non- overlapping case

Baseband resources availablefor R99 users

HSUPA BTS

processing

sets

One HSUPA BTS Processing Set (equivalent

of 48 R99 CE) is always available for R99

users and HSUPA users*

* Note: 48 CE in each

LCG is always

dynamic (even without

license overlapping)


17/36


For internal use


BaseBand resources allocationOverlapping baseband capacity and static resources reservation

Rel99 CE licensesHSUPA BTS

processing

sets

Baseband resources available for HSUPA users

only!

Overlapping baseband capacity can be

dynamically share between HSUPA users and

R99 user*

System Module Rel.2

Rel 99 users

HSDPA

commissioned

throughput

HSUPA users

For overlapping Rel99 CE licenses and licensed HSUPA resources, commissioning can be performed in

order to guarantee resources for HSUPA.

NOTE: Up to four HSUPA resource steps can be statically commissioned for HSUPA

Overlapping scenario

* R99 users have always higher priority

HSUPA BTS

Processing sets

48CE

(dynamic)


18/36


For internal use


HSUPA resources allocation (1/2)

HSUPA scheduler supports different types of HSUPA users (2msTTI/10ms TTI, F-DPCH/no-FDPCH, CS

Voice over HSPA users) Each type of HSUPA user has different baseband requirements Required Baseband resources for HSUPA scheduler depends on number of CS Voice over HSPA and

HSUPA active users and combined L1 throughput

For HSUPA scheduler baseband resources dimensioning purpose few different tables according to theuser types should be used

In addition for HSUPA users transmitting with 16QAM (F-DPCH or no-FDPCH) additional rule should beapplied. One subunit is required for single 16QAM transmitting user

CS Voice over HSPA users consume Subunits. Max 18 CS Voice over HSPA users are allocated in singleSubunit

# of 16QAM transmitting UE (RU30EP2)

10ms TTI no-FDPCH dimensioning table

10ms TTI FDPCH dimensioning table

2ms TTI FDPCH dimensioning table

2ms TTI no-FDPCH dimensioning table

HSUPA scheduler baseband

resources for CS Voice over HSPA

and HSUPA data users#CS Voice over HSPA users


19/36


For internal use


HSUPA resources allocation (2/2)HSUPA requirements for simultaneous users and throughput

2ms TTI

FDPCH UEs

2ms TTI no-FDPCH UEs

16QAM 2ms

TTI (FDPCH/ no-FDPCH

UEs)

10ms TTI

FDPCH

UEs

HSUPA scheduler

baseband resources for

HSUPA dataand CS Voice

over HSPA users

10ms TTI no-

FDPCH UEs

1 Subunit for single

16QAM transmitting UE

10ms TTI no-FDPCH

dimensioning table

10ms TTI FDPCH

dimensioning table2ms TTI FDPCH

dimensioning table

2ms TTI no-FDPCH UEs

CS Voice

over HSPA

1 Subunit for 18 CS

Voice over HSPA users


20/36


For internal use


HSUPA subunits for 2ms TTI UEsFDPCH feature not activated or no-FDPCH capable UEs (SRB on DCH)

Table presents required number of subunits for HSUPA 2ms TTI no-FDPCH UEs

Note: figures are tentative and will be confirmed after final verification in pilot phase

2ms TTI no-

FDPCH UEs

Table assumes typical use case when the majority of the users are downlink data dominatedand the remaining users are UL data dominated.

HSUPA subunits for 2ms TTI UE in RU30 EP1 (without 16QAM)

Number of

HSUPAUEs

per

scheduler


21/36


For internal use


HSUPA subunits for 2ms TTI UEsFDPCH feature activated and FDPCH capable UEs (SRB on HSPA)

Table presents required number of subunits for HSUPA 2ms TTI FDPCH UEs

2ms TTI

FDPCH UEs

HSUPA subunits for 2ms TTI UE in RU30 EP1 (without 16QAM)

Number of

HSUPA UEs

perscheduler


22/36


For internal use


HSUPA subunits for 10ms TTI UEsFDPCH feature activated and FDPCH capable UEs (SRB on HSPA)

Table presents required number of subunits for HSUPA 10 ms TTI FDPCH UEs

10ms TTI

FDPCH UEs

HSUPA subunits for 10ms TTI UE in RU30 EP1

Number of

HSUPA UEsper

scheduler


23/36


For internal use


HSUPA subunits for 10ms TTI UEsFDPCH not feature activated or no-FDPCH capable UEs (SRB on DCH)

Table presents required number of subunits for HSUPA 10 ms TTI no-FDPCH UEs

10ms TTI no-

FDPCH UEs

HSUPA subunits for 10ms TTI UE in RU30 EP1

Number ofHSUPA UEs

perscheduler


24/36


For internal use


CS Voice over HSPA users consume Subunits. Up to 18 CS Voice over HSPA

users can be allocated in one Subunit

HSUPA subunits for CS Voice over HSPA users

Number of CS Voice over HSPA users Subunit

4 0.25

9 0.5

13 0.75

18 1

Each CS Voice over HSPA user decreases the maximum number of HSPA usersallowed by HSDPA and HSUPA scheduler user pool.

CS Voice over HSPA user does not consume Rel99 CE licenses. Each CS Voiceover HSPA user decreases the throughput and the number of users allowed bythe HSUPA Processing Set and the HSDPA Processing Set.

A CS Voice over HSPA user (as a regular HSPA user) has the same priority asHSPA user


25/36


For internal use


HSUPA dimensioning (1/2)RU30EP1/EP2 BB resources reservation

To calculate the subunits reservation inside System Module Rel.2 for mixed user type case, (F-DPCH/noFDPCH/2ms TTI/10msTTI users, 16QAM transmitting users and CS Voice over HSPA), the following rule

should be applied:

Where:

F-DPCH_2msTTI_Subunits = subunits required for HSUPA F-DPCH 2ms TTI usersF-DPCH_10msTTI_Subunits = subunits required for HSUPA F-DPCH 10ms TTI users

No-F-DPCH_2msTTI_Subunits = subunits required for HSUPA no-F-DPCH 2ms TTI users

No-F-DPCH_10msTTI_Subunits = subunits required for HSUPA no-F-DPCH 10ms TTI users

16QAM_2msTTI_Subunits = subunits required for HSUPA 16QAM simultaneously transmitting UEs (RU30EP2)

CS_Voice_over_HSPA_Subunitssubunits required for CS Voice over HSPA users.

HSUPA_Subunits = F-DPCH_2msTTI_Subunits + F-DPCH_10msTTI_Subunits +

no-F-DPCH_2msTTI_Subunits + no-F-DPCH_10msTTI_Subunits + 16QAM_2msTTI_Subunits

+ CS_Voice_over _HSPA_Subunits

Note: in some cases presented rule may lead to overestimation of baseband resources


26/36


For internal use


HSUPA dimensioning (2/2)RU30EP1/EP2 HSUPA Processing Sets requirements

In order to reach simultaneously certain number of HSUPA users (data + CS Voice over HSPA) and certaincombined L1 throughput , the following formula should be used to calculate required number of HSUPA BTS

ProcessingSets

Where:

HSUPA subunitssubunits required for HSUPA purpose (see formula)

Minimum amount of HSUPA BTS Processing Setsnumber of HSUPA BTS Processing Sets calculated for

certain HSUPA throughput or number of HSUPA users (see formula below)

Number of HSUPA BTS Processing Sets = max ( HSUPA subunits/ 1,5 ; Minimum amount of

HSUPA BTS Processing Sets)

Minimum amount of HSUPA BTS Processing Sets =

max ( Roundup ( Number_of_HSUPA_users / 24) ; Roundup(HSUPA_throughput / 5,8) )

Where:

Number_of_HSUPA_usersNumber of HSUPA users (data + CS Voice over HSPA)

HSUPA_throughputHSUPA users (data + CS Voice over HSPA) throughput [Mbps]


27/36


For internal use


HSUPA BTS Processing Set resources allocationHSUPA users/throughput distribution

Available HSUPA BTS processing set resources needs to be distributed among HSUPA schedulers

If Baseband pooling is used then BTS will divide HSUPA licenses between LCGs according tocommissioned share (HSUPA user/throughput license share). Sum of LCG shares is always 100%.

HSUPA licence share is performed with HSUPA BTS processing set licence granularity. If licenses

cannot be share equally between LCGs, in that case BTS will divide higher amount of licenses to

LCG starting from lowest LCG number. E.g.: if commissioned shares are 50% / 50% and there are 5

HSUPA licenses, then LCG1 gets 3 licenses and LCG2 gets 2 licenses.

If HSUPA scheduler is present in both System Modules (same LCG), in this case BTS will allocateHSUPA licenses proportionally to baseband capacity for traffic use of each system module, with

BTS processing set granularity.


28/36


For internal use


MultiRAB scenario in RU30HSPA + AMR

MiltiRAB call -> HSPA + AMR

R99 HSDPA HSUPA R99

- AMR call is served with HSUPA resources (Rel.99 CE licenses not needed)

- if HSPA user = non-FDPCH user => no impact on baseband consumption

- if HSPA user = FDPCH user => HSPA user should be treated (-> impact onHSUPA resources) as HSPA non-FDPCH user

- AMR call needs to be served at the same System Module as HSDPA scheduler

- Additional R99 resources (UL/DL) needs to be allocated for AMR call

- (1 Rel.99 CE license needed)

HSPA call (UL:HSUPA,

DL: HSDPA)

HSPA call (UL:R99,

DL: HSDPA)

AMR callAMR call

HSPA call(UL:HSUPA,

DL: HSDPA)

HSPA call

(UL:R99,

DL:

HSDPA)

SM rel.2 SM rel.2

Exemplary BTS

configuration:

- SM rel.2 + SM rel.2, 1LCG,

Frequency mapping to HW

not used


29/36


For internal use


Network ParametersRAN21231 Gigabit Baseband


30/36


31/36


For internal use


New network planning parametersHSUPA BB decoding capacity

Abbreviated name hsupaBbDecodCapacity

Parameter name HSUPA BB decoding capacity

Data type -

Description Defines Minimum HSUPA decoding capacity per LCG in Mbit/s.

Parameter group -

Classification LCELGW

Range and step0 Mbit/s (0), less than 1.4 Mbit/s (1), 1.4 Mbit/s (2),

2.8 Mbit/s (3), 4.2 Mbit/s (4), 5.6 Mbit/s (5)

Default value 0

Parameter used for static HSUPA commissioning (together with HSUPA BB minimum users parameter)

Static HSUPA baseband resources can not be taken by R99 traffic in case of license overlapping (Rel99CE licenses and HSUPA BTS Processing Sets licenses)


32/36


For internal use


New network planning parametersHSUPA BB minimum users

Abbreviated name hsupaBbMinimumUsers

Parameter name HSUPA BB minimum users

Data type -

Description Defines minimum amount of users allocate to baseband in HSUPA.

Parameter group -


Range and step 0 - 24

Default value 0

Parameter used for static HSUPA commissioning (together with HSUPA BB decoding capacity parameter)

Static HSUPA baseband resources can not be taken by R99 traffic in case of license overlapping (Rel99CE licenses and HSUPA BTS Processing Sets licenses)


33/36


For internal use


New network planning parametersHSUPA user/throughput licence share

Abbreviated name shareOfHSUPALicences

Parameter name HSUPA user/throughput license share

Data type %

Description Parameter defines how many HSUPA licenses belongs to certain LCG. Sum of LCG

shares must be always 100%. No common pool is available. Granularity is one

license. If there is 50%/50% share and 5 lisences, LCG1 gets 3 licenses while LCG2

gets 2 licenses. Parameter have additionally special value -1 which means that

parameter is not in use. Note: Not applicable for rel1 HW.

Parameter group -


Range and step 0 - 100; 1

Default value

Default value of parameter is 100% divided by number of LCGs (max number LCGs

in WN7.0 Flexi is 4). Following default values will be used: 1 LCG => 100%, 2 LCGs

=> 50%, 3 LCGs => 33, 4 LCGs => 25%

LCG 2LCG 1

HSUPA BTS

Processing set

HSUPA BTS

Processing set

HSUPA BTS

Processing setHSUPA BTS

Processing set

HSUPA BTS

Processing setDefines HSUPA license

distribution among LCGs


34/36


For internal use


New network planning parametersPIC Pool

Abbreviated name picPool

Parameter name PIC Pool

Data type Number

Description With this parameter operator is able to commission PIC pools in use.

Parameter group

Classification Operation and Maintenance

Range and step 1...4, step 1

Default value -

PIC Pool 1

PIC Pool 2

PIC Pool 3

PIC Pool 4

Parameter value:picPool (1)

Master System

Module

Extension

System Module

Parameter value:picPool (2)Parameter value:

picPool (3)Parameter value:picPool (4)

N k l i


35/36


For internal use


Network planning parametersHSUPA resource allocation, HSUPA BTS Processing sets

HSUPA BB minimum users

HSUPA BB decoding capacity

HSUPA BTS Processing Set 1one processing set allows to reach 24 HSUPA users and 5,8Mbps


36/36

For internal use

Thank you

Documents

Flexi 1Gb BB - Part 4 HSUPA Aspects 4