Baseband Dimensioning_RU40 (1).pdf

(1)

Baseband Dimensioning

(2)

Module Objectives

At the end of the

At the end of the module you will be

module you will be able to:

able to:

•

• Recall the baseband capacity of the Flexi Multiradio BTS (Flexi System Module

Recall the baseband capacity of the Flexi Multiradio BTS (Flexi System Module

rel.3 and Rel2) and Flexi

rel.3 and Rel2) and Flexi Lite BTS

Lite BTS (optional material)

(optional material)

•

• Perform baseband allocation/dime

Perform baseband allocation/dimensioning rules for R99, HSDPA

nsioning rules for R99, HSDPA & HSUPA

& HSUPA

traffic

(3)

Module Objectives

At the end of the

At the end of the module you will be

module you will be able to:

able to:

•

• Recall the baseband capacity of the Flexi Multiradio BTS (Flexi System Module

Recall the baseband capacity of the Flexi Multiradio BTS (Flexi System Module

rel.3 and Rel2) and Flexi

rel.3 and Rel2) and Flexi Lite BTS

Lite BTS (optional material)

(optional material)

•

• Perform baseband allocation/dime

Perform baseband allocation/dimensioning rules for R99, HSDPA

nsioning rules for R99, HSDPA & HSUPA

& HSUPA

traffic

(4)

Baseband Dimensioning

•• RU40 Licensing Aspects

RU40 Licensing Aspects

•• Rel99 CE license

Rel99 CE license

•• HSDPA BTS Processing Sets license

HSDPA BTS Processing Sets license

•• HSUPA BTS Processing Sets license

HSUPA BTS Processing Sets license

•• CCCH Processing Sets license

CCCH Processing Sets license

•• Baseband Dimensioning Essentials

Baseband Dimensioning Essentials

•• RU40 System Modules capacity

RU40 System Modules capacity

•• Local Cells Grouping

Local Cells Grouping

•• Frequency based pooling

Frequency based pooling

•• Sector based pooling

Sector based pooling

(5)

Baseband Dimensioning

• RU40 Baseband Dimensioning

• Flexi System Module rel.3 Baseband dimensioning

• System Module rel.3 capacity • LCG configurations

• Common Control Channels and R99 dimensioning • HSDPA dimensioning

• HSUPA dimensioning

• Flexi System Module rel.2 Baseband dimensioning

• System Module rel.2 capacity

• Common Control Channels and R99 dimensioning • HSDPA dimensioning

• HSUPA dimensioning

• Flexi Lite BTS overview and capacity

• Flexi Lite BTS overview • LCG configurations • Flexi Lite BTS capacity

(6)

(7)

Licensing aspects (1/8)

General information

•

In RU40 for Flexi System Module Rel.2 and System Module rel.3 CE licenses are valid for R99 traffic

•

HSDPA and HSUPA schedulers do not consume CE licenses

•

HSDPA/HSUPA will have own capacity licenses that are called respectively ‘HSDPA BTS processing sets 'and ‘HSUPA BTS processing set’

•

HSUPA and HSDPA schedulers located at System Module rel.1 (FSMB) still requires CE licenses RU40 Licensing aspects

HSUPA users / throughput – HSUPA BTS Processing Sets HSDPA users / throughput – HSDPA BTS Processing Sets

R99 (DCH, A-DCH) traffic – Rel99 CE licenses

SM rel.3 SM rel.2 HSDPA Processing sets HSUPA Processing sets Rel99 CE

(8)

Licensing aspects (2/8)

Rel99 CE licenses

•

Supported by Flexi System Module Rel.1 (FSMB), Rel.2 (FSMC/D/E) and Rel.3 (FSMF)

•

For HW rel.2 and rel.3 Rel99 CE licenses defines maximum capacity for R99 traffic

•

System Module rel.2 and rel.3 HSPA schedulers do not consume anymore R99 CE licenses

•

In case when additional CCCH resources are required for System Module rel.2 (e.g. extended cell case) R99 CE licenses capacity is decreased by amount of additional Rel99 CE required for CCCH processing

•

Note: HSPA schedulers allocated at System Module rel.1 still consume CE licenses (called in now - R99 CE licenses)

(9)

Licensing aspects (3/8)

Rel99 CE licenses

Rel99 CE licenses consumption:

•

CCCH resources (if needed e.g. extended cell case) from pure System Module rel.2 BTS

•

R99 users (PS, CS services)

•

A-DCH (Associated DCH)

•

SRB for HSDPA user Rel99 CE licenses

(10)

Licensing aspects (4/8)

HSDPA BTS processing set

•

Each HSDPA BTS processing set has certain capacity of users and HSDPA throughput

•

There are three types of HSDPA BTS processing set licenses – from 1 to 3

•

Customers can freely select set 1 licenses or set 2 and set 3 licenses for increasing licensed HSDPA throughput and maximum HSDPA user amount

•

HSDPA BTS processing set licenses are incremental as R99 CE licenses

•

Note: HSDPA processing sets 2 and 3 overwrite HSDPA license Set 1 (e.g. when set 2 is bought maximum capacity is as set 2 defines (set 1 capacity is not summed into set 2)

•

Processing set does not guarantee the maximum user amount and throughput but additional features are needed (e.g. 64-QAM, 10/15 HS-PDSCH codes, 72HSPA users per cell)

(11)

Licensing aspects (5/8)

HSDPA BTS processing set

HSDPA Processing Set Max number of HSDPA users_{per BTS} Max HSDPA throughput per_BTS

HSDPA BTS processing set 1 32 7,2 Mbps HSDPA BTS processing set 2 72 21 Mbps HSDPA BTS processing set 3 72 84 Mbps

Operator can activate combination of different HSDPA processing sets

e.g. 2 x HSDPA BTS processing set 2 + 1 x HSDPA BTS processing set 3 = 2* 72 UEs / 2* 21Mbps + 1*72 UEs / 1*84Mbps = 216 UEs / 126Mbps

HSDPA BTS processing set

HSDPA BTS Processing set 2 HSDPA BTS Processing set 2 HSDPA BTS Processing set 3 2xPS2+ PS3 216 HSDPA users and 126Mbps HSDPA BTS Processing set 1 HSDPA BTS Processing set 1 HSDPA BTS Processing set 3 PS3 72 HSDPA users and 84Mbps

(12)

Licensing aspects (6/8)

HSUPA BTS processing set

•

In RU40 HSUPA BTS processing set license allows for allocation of 24 HSUPA UEs and 5,8Mbps throughput

•

R99 UEs can be allocated into one HSUPA processing set (per LCG) even there is no R99 CE license (48 Rel99 CE)

•

HSUPA BTS processing set does not enable peak UL throughputs, but it can limit those (as HSDPA BTS processing set does for DL throughput). For achieving peak UL throughputs customer needs to buy separate license for peak throughput features like HSUPA 16QAM.

Operator can activate a few HSUPA processing sets e.g. 6 x HSUPA BTS processing set 1 allows for:

• 6*24 UEs = 144 UEs per BTS and 6*5,8 Mbps = 34,8 Mbps HSUPA BTS processing set

(13)

Licensing aspects (7/8)

HSPA BTS processing set (RU40) – summary

•

HSDPA BTS processing set 1: 32 users and 7.2Mbps

•

HSDPA BTS processing set 2: 72 users and 21Mbps

•

HSDPA BTS processing set 3: 72 users and 84Mbps

•

HSUPA BTS processing set 1: 24 users and 5.8Mbps

Above HSUPA/HSDPA throughputs are peak air interface throughputs of BTS. HSUPA and HSDPA BTS processing sets

(14)

Licensing aspects (8/8)

CCCH Processing Set license (RU40)

CCCH Processing Set

CCCH Processing Set license is valid for System Module rel.3 BTS, including SM rel.3 + SM rel.2

configuration. Pure System Module rel.2 BTS still consumes Rel.99 CE for additional CCCH resources allocation

Each System Module rel.2 and rel.3 includes resources for CCCH processing for basic configurations (e.g. 6cell/10km or 3cell/20km) which does not require any license.

However in certain cases (e.g. higher configuration or higher cell radius) more resources needs to be licensed for CCCH processing from System Module traffic capacity.

In RU40 for System Module rel.3 CCCH Processing Set license is introduced instead of Rel.99 CE licenses.

One CCCH Processing Set corresponds to 1 subunit (System Module rel.2) / 0,5 subunit (System Module rel.3) baseband capacity.

(15)

(16)

Baseband dimensioning process

B B al _l o c a t _i o_n I n p u t p a_r a_m e t er s L C G p o o_l i n g How many LCGs are

required ? BTS configuration

( SM/RF module HW type)

Required features

(e.g. 4 Rx Div, Interference cancellation, DC HSDPA)

Amount of cells

Amount of HSPA users and HSPA throughput

How many cells per LCG ?

CCCH processing resources HSDPA scheduler

resources

HSUPA scheduler static resources DCH/ADCH/SRB resources HSUPA scheduler resources

Traffic

demand

fulfilled ?

Select next bigger configuration or reconfigure Local Cell Grouping No Yes _End Start LCG pooling type ? (Fixed/Flexible/Sector based)

(17)

Baseband allocation and capacity license dimensioning

process

BB allocation BB allocation

CCCH resources

•• Amount of cells Amount of cells •• Req. cell range Req. cell range •• Rx Div type Rx Div type

HSDPA resources

•• Commissioned HSDPA Commissioned HSDPA thr.

thr. (SM rel.2)(SM rel.2)

•• LCG configuration type LCG configuration type (SM rel.3)

(SM rel.3)

•• Amount of MIMO/non- Amount of MIMO/non-MIMO cells

MIMO cells

Static

HSUPA

resources

•• Commissioned HSUPA Commissioned HSUPA thr and users (HSUPA thr and users (HSUPA scheduler static scheduler static resources) resources)

•• Amount of PIC pools Amount of PIC pools

DCH/ADCH/SRB

resources

HSUPA scheduler

resources

•• Amount of HSUPA users Amount of HSUPA users •• HSUPA throughput HSUPA throughput •• Amount of activated Amount of activated HSUPA schedulers HSUPA schedulers Capacity License Capacity License dimensioning dimensioning

Rel99 CE licenses /

CCCH Processing Sets

HSDPA Processing

Sets

(amount and type)

HSUPA Processing

Sets

(amount) (amount)

Rel99 CE licenses

HSUPA Processing

Sets

(amount) (amount)

•• Amount and type of: Amount and type of: - R99 users - R99 users - HSDPA users - HSDPA users (ADCH/SRB) (ADCH/SRB) •• Amount of HSDPA Amount of HSDPA users

users

•• HSDPA throughput HSDPA throughput •• Amount of activated Amount of activated HSDPA schedulers HSDPA schedulers

(18)

Local Cell Grouping

(19)

Local Cell Grouping

LCG description

•

• Local Cell Grouping allows splitting available baseband capacity into baseband pools

Local Cell Grouping allows splitting available baseband capacity into baseband pools

responsible for processing traffic from dedicated group of cells.

•

• Local Cell Grouping may be needed in case of BTSs with many cells, and can be used in Multi

Local Cell Grouping may be needed in case of BTSs with many cells, and can be used in Multi

Operator RAN (MORAN) case.

•

• When Local Cell Grouping is done

When Local Cell Grouping is done –

– available BTS capacity is split among LCG according to

available BTS capacity is split among LCG according to

BTS commissioning

BTS commissioning settings.

settings. Baseband allocation to

Baseband allocation to LCG is

LCG is constant (recommissioning is

constant (recommissioning is

needed to change LCG resources).

•

• With pure HW rel.2/rel.3 (RF + SM) a single LCG covers up to twelve cells. However, when 4-

With pure HW rel.2/rel.3 (RF + SM) a single LCG covers up to twelve cells. However, when

4-way Rx diversity is used, up to six 4-4-way RX diversity cells can be dedicated to one LCG.

way Rx diversity is used, up to six 4-way RX diversity cells can be dedicated to one LCG.

•

• The operator has a possibility to define Local Cell Groups in one of the two different ways:

The operator has a possibility to define Local Cell Groups in one of the two different ways:

•

• Frequency layer basedFrequency layer based •

• Sector basedSector based

LCG3 LCG4 LCG3 LCG4 L L C C G G 1 1 LCG2 LCG2

(20)

(21)

Frequency based pooling (1/3)

General information

• If frequency-layer-based LCG commissioning was selected, then all cells from frequency layer(s)

must be dedicated to the same Local Cell.

• Up to 4 LCGs can be created with pure HW rel.2/rel.3 (RF + SM) case.

• When at least one HW rel.1 is used (RF or SM) then up to 2 LCGs can be created (max 6 cells

per LCG). In this case fixed baseband pooling is possible – single LCG covers whole capacity of

single System Module (e.g. LCG1: FSMD; LCG2: FSME)

• With pure HW rel.2/rel.3 configuration – flexible pooling is possible i.e the BB capacity can be

freely dedicated among LCGs (operators) by defining in commissioning the Access Baseband

Capacity parameter.

System Module RF modules

LCG1:f1

LCG2:f2

LCG2 LCG1 Exemplary BTS

configuration with flexible baseband pooling

(22)

Frequency based pooling (2/3)

General information

LCG1 LCG2

SM rel.2

Fixed BB pooling (e.g. RF rel.1 used)

LCG1 LCG2

SM rel.2

Flexible BB pooling (pure HW rel.2/rel.3 configuration)

LCG1

(23)

Frequency based pooling (3/3)

Requirements/benefits

Frequency baseband pooling requirements:

•

Whole frequency layer must be allocated to given LCG

•

Pure HW rel.2/rel.3 required for flexible baseband pooling

Benefits/constrains:

•

HSPA on both System Modules with more than one LCG

•

LCG baseband capacity can be adjusted according to LCG need (flexible baseband pooling possible with HW rel.2/rel.3 only BTS)

•

More HSUPA schedulers (one HSUPA scheduler per LCG)

(24)

(25)

Sector based pooling (1/2)

General information

• In RU40, operator has a possibility to define Local Cell Groups in one of the two different

commissioning modes:

• Frequency layer based (traditional way - whole frequency layer dedicated to LCG);

• Sector based (whole frequency layer or part of frequency layer dedicated to LCG)

f4 f3 f2 f1 System Modules RF modules LCG1 System Modules RF modules LCG2 LCG1 Example of Frequency based pooling

Examples of Sector based pooling

LCG2

Effect of using sector based pooling might be the same as using frequency based pooling

(26)

Sector based pooling (2/2)

Requirements/benefits

Sector based pooling requirements:

•

Two System Modules rel.2 or System Module rel.3 (or SM rel.3 + SM rel.2)Two System Modules rel.2 or System Module rel.3 (or SM rel.3 + SM rel.2)

•

Pure Rel.2/Rel.3 HW BTS configuration (RF + SM)Pure Rel.2/Rel.3 HW BTS configuration (RF + SM)

-> Two LCGs are created. For each System Module rel.2 separate LCG is created. With System -> Two LCGs are created. For each System Module rel.2 separate LCG is created. With System Module rel.3 up to 2 LCGs can be created.

Module rel.3 up to 2 LCGs can be created.

Benefits/constrains:

•

HSPA on both System Modules with 2 LCGsHSPA on both System Modules with 2 LCGs

•

More HSUPA schedulers (one HSUPA scheduler per LCG) and baseband capacity for HSPA trafficMore HSUPA schedulers (one HSUPA scheduler per LCG) and baseband capacity for HSPA traffic

•

DC-HSDPA possible (DC sectors split between LCGs)DC-HSDPA possible (DC sectors split between LCGs)

•

Increase soft handover factorIncrease soft handover factor

FSM rel.2 FSM rel.2 FSM rel.2 FSM rel.2 FSM rel.2 + FSM rel.2 FSM rel.2 + FSM rel.2 (sector based polling) (sector based polling)

LCG1 LCG1 LCG2 LCG2 D D C C H H S S D D P P A A FSM rel.3 FSM rel.3 FSM rel.3 FSM rel.3 (sector based polling) (sector based polling)

LCG2 LCG2

(27)

Frequency mapping to HW

(28)

Frequency mapping to HW (1/2)

General information

•

• Frequency mapping to HW allows to map whole frequency layer to given System Module. If some frequency layer isFrequency mapping to HW allows to map whole frequency layer to given System Module. If some frequency layer is mapped to a System Module,

mapped to a System Module, the selected System Module has to provide Common Control Channels, HSUPA,the selected System Module has to provide Common Control Channels, HSUPA, and HSDPA processing resources (including A-DCH and SRB resources) for cells from the assigned

and HSDPA processing resources (including A-DCH and SRB resources) for cells from the assigned frequency layer

frequency layer . DCH users from the assigned frequency layer are also allocated at the selected System Module,. DCH users from the assigned frequency layer are also allocated at the selected System Module, however, when the full System Module capacity is occupied, new DCH users can be allocated at the second System however, when the full System Module capacity is occupied, new DCH users can be allocated at the second System Module.

Module. •

• With Frequency mapping to HW it is possible to have HSPA on both System Modules withWith Frequency mapping to HW it is possible to have HSPA on both System Modules with one LCG.one LCG.

LCG1

f1 f1 f2 f2 200/240 HSUPA 200/240 HSUPA users

users per per ExtensionExtension

System Module

200/240 HSUPA

users

users per per MasterMaster

System Module

Frequency mapping to HW can be used only with one LCG scenario Frequency mapping to HW can be used only with one LCG scenario

400/480 HSUPA users per LCG

(29)

Frequency mapping to HW (2/2)

Requirements

Frequency mapping to HW requirements:

•

Two System Modules (where at least one Rel.2 System Module required)

•

One LCG scenario (RU30 onwards)

•

More than 1 carrier

Benefits/constrains:

•

HSPA on both System Modules with one LCG scenario

•

More HSPA schedulers: Two HSUPA schedulers/four HSDPA schedulers –> (240 HSUPA/480 HSDPA users per single System Module)

•

More BB resources for HSPA -> (up to 15 subunits per single System Module (single HSUPA scheduler) -> 2x15 = 30 subunits per BTS)

•

Baseband pooling for R99 traffic (R99(f1) -> MSM or ESM; R99(f2) -> MSM or ESM)

•

Possible with multiple carriers HSUPA (f1,f2) HSDPA (f1,f2) A-DCH (f1,f2) DCH (f1,f2,f3) HSUPA (f3) HSDPA (f3) A-DCH (f3) DCH (f1, f2,f3) MSM ESM R99 traffic of all carriers served ESM MSM f3 f2 f1

(30)

RU40 Baseband Dimensioning

Flexi System Module rel.3 Baseband

dimensioning

(31)

System Module rel.3 capacity

(32)

System Module rel.3 capacity(1/3)

System Module Rel.3 capacity - number of subunits

•

System Module rel.3 provides capacity of 5.5 Rel.3 subunitsSystem Module rel.3 provides capacity of 5.5 Rel.3 subunits

•

Available resource Available resources (subus (subunits) canits) can be un be used for sed for CCCH processinCCCH processing, HSg, HSDPDPA schA schedulers edulers processing, processing, HSUPHSUPAA users and thr. processing, R99 users processing and interference cancellation processing

users and thr. processing, R99 users processing and interference cancellation processing

•

Please note that each System Module rel.3 contains CCCH processing resources required forPlease note that each System Module rel.3 contains CCCH processing resources required for ‘Basic‘Basic Configurations’

Configurations’ (e.g. 6 cells/10km or (e.g. 6 cells/10km or 3cells/20km3cells/20km – – 2way Rx Div) included in the System Module rel.3 capacity 2way Rx Div) included in the System Module rel.3 capacity Number of cells

Number of cells

FSMF without capacity

extension

extension submodulsubmoduleses

(subunits) (subunits) 1 1 – – 6 6 5,55,5 7 7 – –1212 5 + 0,55 + 0,5

Table assumes 10km cell range and 2way Rx Div

(33)

System Module rel.3 capacity(2/3)

System Module Rel.3 capacity - number of subunits

•

One type of Extension submodule available for WCDMA: FBBAOne type of Extension submodule available for WCDMA: FBBA

•

Extension submodule are used to extend System Module capacityExtension submodule are used to extend System Module capacity

•

Up to 2 Extension submodules can be used to extend capacity of single System Module rel.3Up to 2 Extension submodules can be used to extend capacity of single System Module rel.3

2x Capacity expansion submodule 2x Capacity expansion submodule

(FBBA -> WCDMA) (FBBA -> WCDMA) Expansion Expansion Submodule Submodule Available Available Subunits Subunits FBBA FBBA 66

(34)

(35)

LCG Configurations (1/14)

LCG configuration types

LCG configuration type might be commissioned using HSPA setting parameter

•

System Module rel.3 LCG might be commissioned to one out of the three configurations:

•

Rel99 only (up to 12 cells)

•

Support of UMTS Rel.99 services, no support for HSPA

•

Small HSPA configuration (up to 6 cells)

•

Providing HSPA processing up to 6 HSPA cells (one HSDPA and HSUPA scheduler)

•

Normal HSPA configuration (up to 12 cells)

•

Providing HSPA processing up to12 HSPA cells (two HSDPA and one HSUPA scheduler) System Module rel.3 LCG configuration

Note that LCG configuration type commissioning is optional. By default Normal HSPA configuration is assumed

(36)

LCG Configurations (2/14)

LCG configuration types

System Module rel.3 LCG configuration

HSDPA scheduler BB resources allocation LCG configuration type LCG2: Small HSPA configuration LCG3: Normal HSPA configuration LCG1: Rel99 only configuration HSPA + R99 (up to 6 cells) HSPA + R99 (up to 12 cells) Rel99 only (up to

12 cells)

Exemplary

configuration - BTS with 3 different LCG types

Single LCG supports up to 12 cells (2 way Rx div) / 6 cells (4 way Rx div).

One restriction concerns Small HSPA configuration where up to 6 cells (2way/4way Rx Div) are supported per LCG

Optional CCCH processing baseband resources for additional

CCCH requirements (e.g. higher cell range)

(37)

LCG: Small HSPA configuration LCG: Normal HSPA configuration LCG: Rel99 only configuration HSDPA scheduler resources (1x HSDPA scheduler)

LCG capacity (e.g. LCG1: FSMF – 5,5 subunits)

HSDPA scheduler resources

(2x HSDPA schedulers) LCG configuration (Min_HSDPA_resources) Small 0,5 Normal 1 HSDPA_scheduler_resources = max { (Cells_factor / 2) - 0,5 ; Min_HSDPA_resources } + 0,125 where:

Cells_factor = Roundup { [ RoundUp(non-MIMO cells/3) + MIMO cells] / 2 }

LCG Configurations (3/14)

LCG configuration types

(38)

LCG configuration:

Small HSPA or

Normal HSPA

configuration

HSDPA scheduler

Resources

(subunits)

Additional CCCH processing baseband resources HSPA LCG configuration (Small HSPA or Normal HSPA) impact on traffic capacity

LCG Configurations (4/14)

LCG configuration types – impact on capacity

Required amount of baseband resources (so called CCCH pool) depends on amount of

cells, cell range and Rx diversity. One CCCH pool corresponds to 0,5 subunit unless it is

included in HSDPA scheduler resources.

(39)

CCCH processing resources included in FSMF SM capacity LCG1 LCG2 LCG1: Small HSPA configuration LCG2: Normal HSPA configuration

HSDPA scheduler resources

HSDPA scheduler resources 0,5 su (1 x CCCH

Processing Set LK)

Optional CCCH processing BB resources

HSPA LCG configuration (Small HSPA or Normal HSPA) impact on traffic capacity

CCCH Processing Sets license(s)

required to use optional CCCH

processing baseband resources

included in HSDPA scheduler

capacity

LCG Configurations (5/14)

(40)

LCG Configurations (6/14)

LCG configuration types – impact on capacity

HSDPA_scheduler_resources = max { (Cells_factor / 2) - 0,5 ; Min_HSDPA_resources } + 0,125

Where:

Cells_factor = Roundup { [ RoundUp(non-MIMO cells/3) + MIMO cells] / 2 }

LCG

configuration (Min_HSDPA_resources)

Small 0,5

Normal 1

#_CCCH_available_pools = max { Min_HSDPA_resources ; (Cells_factor / 2) – 0,5 } / 0,5

For example: 6 MIMO and 6 non-MIMO cells (3 Rel99 only cells + 3 HSPA non-MIMO cells ); Normal configuration; 1 LCG; 10km cell range

Cells_factor = Roundup { [Round Up (6/3) + 6] / 2 } = Roundup {4} = 4

HSDPA_scheduler_resources = max { (4 / 2) – 0,5 ; 1} + 0,125 = max {1,5 ; 1} + 0,125 = 1,5 + 0,125 = 1,625 #CCCH_available_pools = max { 1 ; 4 / 2 – 0,5} / 0,5 = max { 1 ; 2 – 0,5} / 0,5 = max { 1 ; 1,5} / 0,5 = 1,5 / 0,5 = 3

#Required_CCCH_pools = 2 (12cells/10km cell range/2way Rx div) - > 1 CCCH pool included in SM rel.3 capacity (license not needed) + 1 CCCH pool included in HSDPA scheduler resources (2 CCCH pools still remaining in HSDPA scheduler resources) // 1x CCCH Processing Set licenses required.

LCG configuration

Max number of supported cells

Max number of HSPA cells

Rel99 only 12 0

Small 6 6

Normal 12 12

(41)

LCG Configurations (7/14)

LCG configuration types – impact on capacity (non-MIMO cells)

LCG configuration

Number of HSPA (non -MIMO) cells

per LCG

1st_{LCG [subunits]} 2nd and next LCG

[subunits]

Rel99 only 0 (6 non-HSPA_cells) 0 0,5 (CCCH)

Rel99 only 0 (12 non-HSPA_cells) 0,5 (CCCH) 1 (CCCH)

Small Up to 6 cells 0,625 (HSDPA scheduler)

0,5 (CCCH) + 0,625 (HSDPA scheduler)

= 1,125

Normal Up to 6 cells 1,125 (HSDPA scheduler)

= 1,625

Normal Up to 12 cells 1,125 (HSDPA scheduler)

= 1,625

Table assumes non-MIMO cells, 10km cell range/ 2 way Rx Div. Single System Module rel.3 assumed (e.g. FSMF + FBBA)

2 x CCCH Processing Sets required 1 x CCCH Processing Sets required

(42)

LCG Configurations (8/14)

LCG configuration types – impact on capacity (MIMO cells)

LCG configuration

Number of HSPA (MIMO) cells per LCG

1st_LCG

[subunits] 2nd and next LCG [subunits] Rel99 only 0 (6 non-HSPA cells) 0 0,5 (CCCH)

Rel99 only 0 (12 non-HSPA cells) 0,5 (CCCH) 1 (CCCH)

Small Up to 4 MIMO cells 0,625 (HSDPA scheduler*)

0,5 (CCCH) + 0,625 (HSDPA scheduler*) = 1,125

Small 5 - 6 MIMO cells 1,125 (HSDPA scheduler*)

0,5 (CCCH) + 1,125 (HSDPA scheduler*) = 1,625

Normal Up to 6 MIMO cells 1,125 (HSDPA_scheduler*) 0,5 (CCCH) + 1,125 (HSDPA scheduler*) = 1,625

Normal 7 – 8 MIMO cells 1,625 (HSDPA_scheduler*) 0,5 (CCCH) + 1,625 (HSDPA scheduler*) = 2,125

Normal 9 - 10 MIMO cells 2,125 (HSDPA_scheduler*)

0,5 (CCCH) + 2,125 (HSDPA scheduler + optional CCCH)

= 2,625

Normal 10 - 12 MIMO cells 2,625 (HSDPA_scheduler*)

0,5 (CCCH) + 2,625 (HSDPA scheduler + optional CCCH) = 3,125 2 x CCCH Processing Sets required 1 x CCCH Processing Sets required

(43)

LCG Configurations (9/14)

LCG configuration types – Rel99 only

System Module rel.3 LCG configuration – Rel99 only

Number of cells FSMF 1-6 cells 5½ SU 7-12 cells 5 +½* SU CCCH included in SM rel.3 capacity For >6 cells additional 0,5 subunit and 1x CCCH Processing Set license for CCCH processing is needed

Rel99 only configuration – no need for HSPA allocation

One subunit provides 96 Rel.99 CE

R99 bearers have the same Rel.99 CE consumptions as in RU30 with System Module rel.2

(44)

LCG Configurations (10/14)

LCG configuration types – Rel99 only

System Module rel.3 LCG configuration – Rel99 only

Number of cells Core System Module Expansion Submodule #R99Subunits 1-6 cells FSMF - 5½ FBBA 11½ FBBA +FBBA 17½ 7-12 cells - 5 + ½ FBBA 11 + ½ FBBA +FBBA 17 + ½

Table assumes 10km cell range and 2way Rx Div

(45)

LCG Configurations (11/14)

LCG configuration types – Small HSPA

System Module rel.3 LCG configuration – Small HSPA

Number of cells FSMF 1-6 cells 47/ 8 SU CCCH included in SM rel.3 capacity

Small HSPA configuration – one HSDPA and one HSUPA scheduler available supporting up to 6 HSPA cells

One HSDPA scheduler supports:

•

up to 6 HSPA cells

•

Up to 240 active users

•

Up to 252 Mbps

One HSUPA scheduler supports:

•

up to 6 HSPA cells

•

(46)

LCG Configurations (12/14)

LCG configuration types – Small HSPA

System Module rel.3 LCG configuration – small HSPA

Number

of cells Core Module

Extension Submodule Subunits Up to 6 HSPA cells FSMF - 47/ 8 SU FBBA 107/ 8 SU FBBA +FBBA 167/ 8 SU

(47)

LCG Configurations (13/14)

LCG configuration types – Normal HSPA

System Module rel.3 LCG configuration – Normal HSPA

Number of cells FSMF 1-6 cells 43/ 8 SU 7-12 cells 43/ 8 SU ??? CCCH included in SM rel.3 capacity CCCH baseband resources (CCCH pools) for additional 6 cells available with Normal HSPA configuration but additional CCCH

Processing Set license is required

Normal HSPA configuration – two HSDPA and one HSUPA scheduler available supporting up to 12 HSPA cells

Two HSDPA scheduler supports:

•

up to 12 HSPA cells

•

Up to 2 x 240 active users

•

Up to 2 x 252 Mbps*

One HSUPA scheduler supports:

•

up to 12 HSPA cells

•

(48)

LCG Configurations (14/14)

LCG configuration types – Normal HSPA

System Module rel.3 LCG configuration – Normal HSPA

Number

of cells Core Module

Extension Submodule Subunits Up to 12 HSPA cells FSMF - 43/ 8 SU FBBA 103/ 8 SU FBBA +FBBA 163/ 8 SU Table assumes 10km cell range and 2way Rx Div

(49)

(50)

HSDPA scheduler (1/2)

HSDPA scheduler details

•

HSDPA scheduler supports up to 6 cells, 240 active users and up to 252Mbps

•

Comparing to System Modules rel.2, System Module rel.3 HSDPA scheduler does not consume any additional baseband resources to reach required throughput

HSDPA scheduler

Combined Maximum throughput for HSDPA schedulers located at

System Module Rel.2

HSDPA baseband capacity reservation (number of subunits)

0 Mbps HSDPA schedulers not activated 42 Mbps 2 84 Mbps 2 126 Mbps 3 168 Mbps 3 210 Mbps 4 252 Mbps 4 294 Mbps 5 336 Mbps 5 378 Mbps 6 420Mbps 6 462 Mbps 7 504 Mbps 7

Baseband resources required by HSDPA scheduler (System Module rel.2)

0Mbpsca pacity gain

Up to 252Mbps / scheduler

Additional baseband resources not required by

HSDPA scheduler (System Module rel.3)*

* Only A-DCH/SRB CE resources needed for HSDPA users (UL:R99

(51)

• The following HSDPA throughput step values are available: from 1 up to 35 • Each step refers to 7.2Mbps (e.g. 1 - 7.2Mbps; 2 - 14.4Mbps, etc)

• Throughput step is used to distribute/limit the HSDPA licensed throughput among schedulers • Maximum HSDPA Throughput Step commissioning is optional

• If commissioning is not done, then 84Mbps is allocated to every 1-6 non-MIMO cells or 1-3 MIMO cells

HSDPA scheduler (2/2)

Commissioning the Maximum HSDPA Throughput

HSDPA throughput steps HSDPA throughput Mbps 1 7.2 2 14.4 3 21.6 … 6 43.2 7 50.4

• Comparing to Flexi SM Rel.2 there is no HSDPA throughput step=0 (scheduler activation step) • HSDPA scheduler allocation is done with “Small HSPA” or “Normal HSPA” Configuration

HSDPA throughput steps (continued) HSDPA throughput Mbps 8 57.6 … … 13 93.6 14 100.8 … … 35 252

(52)

(53)

Common Control Channels

General information

•

Processing of Common Control Channels (CCCH) in certain cases may require certain amount of licenses (CCCH Processing Set)

•

Required amount of baseband resources ( so called CCCH pool) allocated for CCCH processing depends on:

•

Number of cells

•

Cell range

•

Receive diversity mode

•

One CCCH pool corresponds to 0,5 subunit unless it is included in HSDPA scheduler resources.

•

Each LCG requires at least one CCCH pool (0,5 subunit) to be allocated at LCG capacity unless it is included in System Module rel.3 capacity. Any additional CCCH processing requirements (e.g. extended cell range case or more than 6 cells) can be handled with:

 CCCH pools included in HSDPA scheduler resources (CCCH Processing Set license needed)

 additional CCCH pools licensed from SM rel.3 capacity (CCCH Processing Set license needed)

•

CCCH pool requires CCCH license (CCCH Processing Set) for activation DL 1 x P-SCH 1 x S-SCH 1 x P-CCPCH 1 x P-CPICH 1 x PICH 1 x AICH 3 x S-SCCPCH UL PRACH

(54)

CCCH processing resources allocation

CCCH baseband resources allocation

1) CCCH processing resources

included in SM rel.3 capacity (available for 1 LCG). Additional LCG requires 1 CCCH pool (0,5 subunit)

One CCCH pool included in FSM rel.3

2) LCG configuration type (Small HSPA and Normal HSPA

configuration only)

License not needed

X amount of CCCH pool(s) included in LCG configuration resources License needed (CCCH Processing Set(s)) 3) LCG capacity resources allocation for CCCH processing

One CCCH pool = 0,5 subunit License needed (CCCH Processing Set(s)) Small

HSPA Normal HSPA

1 subunit CCCH pool CCCH processing baseband capacity CCCH processing license capacity

More CCCH processing resources needed ( e.g. high number of cells or higher cell range) ?

Still more CCCH processing resources needed ( e.g. high number of cells/higher cell range) or R99 Only

LCG config.?

Small

HSPA Normal HSPA

No

Yes

No

Basic configurations for 1 LCG (e.g. 6cell/10km, 3 cells/20km One CCCH pool = 0.5 subunit License needed (CCCH Processing Set(s)) e.g. second LCG

(55)

CCCH processing resources allocation

Example 1

Note that CCCH processing resources are LCG specific FSMF + FBBA Example: FSMF + FBBA, 2 LCGs:

– 1st_{LCG 3 cells/20km/2way Rx Div, R99 Only configuration}

– 2nd_{LCG 6 cells/20km/2way Rx Div, Small HSPA configuration (6 non-MIMO cells)}

LCG 1 LCG 2

LCG1 – 3cells/20km cell/2way Rx Div -> 0 CCCH Processing Set licenses needed

-> 3 cells/20km/2way Rx Div supported with CCCH Processing resources included in SM rel.3 capacity

-> 3 cells/20km/2way Rx Div supported with 1 CCCH Processing pool (0,5 subunit) -> 1 CCCH Processing Set required

-> 3 cells/20km/2way Rx Div supported with 1 CCCH pool included in HSDPA scheduler resources (0 additional subunit needed) -> 1 CCCH Processing Set required

#_CCCH_available_pools = max { Min_HSDPA_resources ; (Cells_factor / 2) – 0,5 } / 0,5 = max {0,5 ; 1 / 2 - 0,5} / 0,5 = 1

Number of additional CCCH processing pools available with Small HSPA configuration:

Cells_factor = Roundup { [ RoundUp(non-MIMO cells/3) + MIMO cells] / 2 } = 1 Min_HSDPA_resources = 0,5

(56)

CCCH processing resources allocation

Example 2

Note that CCCH processing resources are LCG specific FSMF + FBBA Example: FSMF + FBBA, 2 LCGs:

– 1st_{LCG 6 cells/20km/2way Rx Div, R99 Only configuration}

– 2nd_{LCG 6 cells/20km/2way Rx Div, Normal HSPA configuration (6 non-MIMO cells)}

LCG 1 LCG 2

-> 3 cells/20km/2way Rx Div supported with CCCH Processing resources included in SM rel.3 capacity

-> 3 cells/20km/2way Rx Div supported with 1 CCCH pool included in HSDPA scheduler resources (0 additional subunit needed) -> 1 CCCH Processing Set required

#_CCCH_available_pools = max { Min_HSDPA_resources ; (Cells_factor / 2) – 0,5 } / 0,5 = max {1 ; 1 / 2 - 0,5} / 0,5 = 2

Number of additional CCCH processing pools available with Normal HSPA configuration (LCG2):

Cells_factor = Roundup { [ RoundUp(non-MIMO cells/3) + MIMO cells] / 2 } = 1

Min_HSDPA_resources = 1 1 CCCH pool (included in HSDPA

(57)

Common Control Channels (CCCH)

CCCH Processing pool

• Number of cells with the certain cell radius & RxDiv mode that can be served with single CCCH pool can be verified with the formula:

i - # of cells (1-6)

Cell range – user cell r adius in km rounded up to next 5km # of signatures – max number of preamble signatures 1=< z =<4 where:

R x =4 (r2ay Rx Div); R x =2 (2way Rx Div)







cells of i i i

*

#

of

Signature

s

*

Rx)

480 Range

(Cell

_ _ # 1

• If the condition above is fulfilled, than the cells configuration can be served with one CCCH processing pool

• Note that depending on the configuration (Small HSPA or Normal HSPA ) the number of already available CCCH pools is different (see slide)

• Note that CCCH pool is active only with corresponding CCCH Processing Set license.

2 way Rx 4 way Rx 0km<r<60km 60km<r<=120km 120km<r<180km # of signatures =4 # of signatures =2 # of signatures =1 0km<r<30km 30km<r<=60km 60km<r<120km # of signatures =4 # of signatures =2 # of signatures =1

(58)

Common Control Channels (CCCH) for typical configurations

LCG configuration type 3cells/20km 6cells/10k m 6cells/20km 9cells/10k m 9cells/20 km 12cells/10 km 12cells/20 km R99 Only 0 CCCH Processing Sets /0 subunit 0 CCCH Processing Sets /0 subunit 1 CCCH Processing Sets /0.5 subunit 1 CCCH Processing Sets /0.5 subunit 2 CCCH Processing Sets /1 subunit 1 CCCH Processing Sets /0.5 subunit 3 CCCH Processing Sets /1.5 subunit Small HSPA 0 CCCH Processing Sets /0 subunit 0 CCCH Processing Sets /0 subunit 1 CCCH Processing Set /0 subunit - - - -Normal HSPA 0 CCCH Processing Sets /0 subunit 0 CCCH Processing Sets /0 subunit 1 CCCH Processing Sets /0 subunit 1 CCCH Processing Set /0 subunit 2 CCCH Processing Sets /0 subunit 1 CCCH Processing Set /0 subunit 3 CCCH Processing Sets /0.5 subunit Normal HSPA (MIMO cells assumed) 0 CCCH Processing Sets /0 subunit 0 CCCH Processing Sets /0 subunit 1 CCCH Processing Sets /0 subunit 1 CCCH Processing Set /0 subunit 2 CCCH Processing Set /0 subunit 1 CCCH Processing Set /0 subunit 3 CCCH Processing Set /0 subunit 1 LCG assumed, using 1 CCCH pool

(59)

Release 99 Dimensioning

R99 bearers consumptions

•

R99 traffic consumes Rel99 CE licenses. Same R99 dimensioning rules are used as in RU20 EP1

•

Two improvements already in RU20 EP1

• PS256 kbps = 6 Rel99 CE (was 9 CE in RU20) • PS384 kbps = 8 Rel99 CE (was 12 CE in RU20)

1) AMR codecs 12.2, 7.95 and 5.90 and 4.75 kbps supported 2) WB-AMR codecs 12.65, 8.85 and 6.6 kbps supported

Amount of required Rel.99 CE =

Max (Ʃ DL Rel.99 CE; Ʃ UL Rel.99 CE)

(60)

Release 99 Dimensioning

R99 bearers consumptions - Example

Rel. 99 CE dimensioning example: UL / DL

20 x AMR 12.2 users 20 / 20 Rel.99 CE 2 x PS I/B 64/128kbps (UL/DL) 8 / 8 Rel.99 CE 1 x PS I/B 128/256kbps (UL/DL) 4 / 6 Rel.99 CE 1 x PS I/B 384/384kbps (UL/DL) 8 / 8 Rel.99 CE

Sum: 40 / 42 Rel.99 CE

Amount of required Rel.99 CE = max (40 ; 42) = 42 Rel.99 CE Amount of required Rel.99 CE =

Max (Ʃ DL Rel.99 CE; Ʃ UL Rel.99 CE)

Note that example concerns R99 scenario only. Note that all Rel.99 CE requirements (additional CCCH and A-DCH/SRB resources (HSDPA)) should be also included in the formula p resented above

(61)

(62)

HSUPA scheduler capacity

Small HSPA and Normal HSPA configuration

•

HSUPA scheduler supports:

•

12 HSUPA cells

•

Up to 240 HSUPA data/CS Voice over HSPA users

•

Up to 12x11.5Mbps=138Mbps (HSUPA 16QAM)

•

Small HSPA configuration (one HSDPA scheduler – 240 HSDPA users, one HSUPA scheduler – 160 HSUPA users) provides:

•

Up to 6 HSPA cells

•

Up to 160 HSUPA data users/CS Voice over HSPA users

•

Normal HSPA configuration (two HSDPA schedulers – 2x 240 HSDPA users, one HSUPA scheduler – 240 HSUPA users) allows to reach:

•

Up to 12 HSPA cells

(63)

• HSUPA baseband allocation is done with HSUPA Resource Steps

HSUPA Consumption (1/6)

HSUPA baseband allocation

Exemplary figure

HSUPA BTS

Processing sets Rel.99 CE licenses Rel99 CE

HSUPA thr., users

• Each HSUPA Resource Step is dynamically utilized based on traffic need (HSUPA user entering a cell)

• Processing capacity of each HSUPA Resource Step provides certain throughput for a certain number of users

Statically commissioned with “HSPA Normal” configuration

HSDPA scheduler

(64)

HSUPA Consumption (2/6)

HSUPA baseband allocation

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 data users 10ms TTI no-FDPCH UEs

1 subunit for three 16QAM transmitting UE 10ms TTI no-FDPCH dimensioning table 10ms TTI FDPCH dimensioning table 2ms TTI FDPCH dimensioning table 2ms TTI no-FDPCH dimensioning table CS Voice over HSPA users

(65)

HSUPA Consumption (3/6)

HSUPA baseband allocation

Number of HSUPA

UEs per scheduler <1.0 Mbps 1.0 Mbps 2.0 Mbps 2.9 Mbps 4.3 Mbps 5.8 Mbps 7.2 Mbps 8.7 Mbps 10.1 Mbps 1 0,125 0,125 N/A N/A N/A N/A N/A N/A N/A 2 0,125 0,125 0,125 0,25 N/A N/A N/A N/A N/A 3~4 0,125 0,25 0,25 0,25 0,25 0,375 N/A N/A N/A 5~6 0,125 0,25 0,25 0,25 0,25 0,375 0,375 0,5 N/A 7~8 0,125 0,25 0,375 0,375 0,375 0,375 0,5 0,5 0,625 9~10 0,125 0,25 0,375 0,5 0,5 0,5 0,5 0,625 0,75 11~12 0,25 0,25 0,375 0,5 0,5 0,5 0,5 0,625 0,75 13~14 0,25 0,375 0,375 0,5 0,625 0,625 0,625 0,625 0,75 15~16 0,25 0,375 0,5 0,5 0,625 0,75 0,75 0,75 0,75 17~18 0,25 0,375 0,5 0,5 0,625 0,75 0,75 0,75 0,75 19~20 0,25 0,375 0,5 0,625 0,75 0,75 0,875 0,875 0,875 21~22 0,375 0,375 0,5 0,625 0,75 0,875 0,875 0,875 0,875 23~24 0,375 0,375 0,5 0,625 0,75 0,875 1 1 1 25~26 0,375 0,375 0,5 0,625 0,75 0,875 1 1,125 1,125 27~28 0,375 0,375 0,625 0,625 0,75 0,875 1 1,125 1,125 29~30 0,375 0,375 0,625 0,75 0,875 1 1,125 1,25 1,25 31~32 0,5 0,5 0,625 0,75 0,875 1 1,125 1,25 1,375 33~34 0,5 0,5 0,625 0,75 0,875 1 1,125 1,25 1,375 35~36 0,5 0,5 0,625 0,75 0,875 1 1,125 1,25 1,375 37~38 0,5 0,5 0,625 0,75 0,875 1 1,25 1,375 1,375 39~40 0,5 0,5 0,625 0,75 1 1,125 1,25 1,375 1,5 41~44 0,625 0,625 0,75 0,875 1 1,125 1,25 1,375 1,5 45~48 0,625 0,625 0,75 0,875 1 1,25 1,375 1,5 1,5 49~52 0,75 0,75 0,75 0,875 1,125 1,25 1,375 1,5 1,625 53~56 0,75 0,75 0,75 0,875 1,125 1,25 1,375 1,5 1,625 57~60 0,75 0,75 0,75 1 1,125 1,375 1,5 1,625 1,75 61~64 0,875 0,875 0,875 1 1,25 1,375 1,5 1,625 1,75 65~68 0,875 0,875 0,875 1,125 1,25 1,375 1,625 1,75 1,875 69~72 1 1 1 1,125 1,25 1,5 1,625 1,75 1,875 73~76 1 1 1 1,125 1,25 1,5 1,625 1,75 2 77~80 1 1 1 1,125 1,375 1,5 1,75 1,875 2 81~100 1,25 1,25 1,25 1,25 1,5 1,75 1,875 2,125 2,25 101~120 1,5 1,5 1,5 1,5 1,625 1,875 2,125 2,25 2,5 10ms TTI FDPCH UEs

Part of HSUPA dimensioning

table presenting HSUPA

subunits required for

FDPCH 10ms TTI users

Whole HSUPA dimensioning

tables can be found in the

appendix

For example: 5,8 Mbps and 70 HSUPA users require 1,5 subunit

(66)

16QAM transmitting UEs

HSUPA baseband allocation

Up to 3 HSUPA 16QAM transmitting UEs can be allocated inside single subunit

Number of HSUPA 16QAM transmitting UEs Required amount of subunits 1 0,375 2 0,625 3 0,875

16QAM – transmitting UEs (e.g. 2 UEs require 0,625 su)

(67)

• CS voice over HSPA user does not consume Rel99 CE license

• CS voice over HSPA user consumes HSDPA and HSUPA resources, i.e. decreases the maximum number of HSPA users by one

• Each CS voice over HSPA user decrease number of HSUPA users allowed by HSUPA license (HSUPA BTS processing set)

and HSDPA license (HSDPA BTS processing set)

CS voice over HSUPA

HSUPA baseband allocation

Number of CS Voice over HSPA

users Subunit (System Module Rel.3) 10 0.125 20 0.25 30 0.375 40 0.5 50 0.625 60 0.75 70 0.875 80 1

Scheduler Max number of CS voice over HSPA users

HSDPA 240

(68)

• FSMF supports up to 3 PIC pools

• 1 PIC pool provides Interference Cancellation on 6 cells @2way Rx Div cells simultaneously • 1 PIC pool provides Interference Cancellation on 3 cells @4way Rx Div cells simultaneously • 1 PIC pool consumes 1 Subunit

HSUPA Interference Cancellation

HSUPA baseband allocation

PIC pool may perform Interference Cancellation on cells from Local Cell Group where is allocated

#PIC pools Cells* that are target for IC Cells* where the IC is performed

Consumed SU

1 6 6 1

(69)

RU40 Baseband Dimensioning

Flexi System Module rel.2 Baseband

dimensioning

(70)

(71)

BaseBand resources allocation (1/9)

System Module Rel. 2 capacity - number of subunits

•

System Module Rel.2 traffic capacity depends on number of commissioned cells. Table below presents number of available subunits for traffic use (or CCCH / interference cancellation processing)

•

Available resources (subunits) can be used for CCCH processing, HSDPA users, thr. and cells processing, HSUPA users and thr. processing, R99 users processing and interference cancellation processing

•

Please note that each SM Rel.2 contains CCCH processing resources required for ‘Basic Configurations’ (e.g. 6 cells/10km or 3cells/20km) included in the System Module rel.2 capacity

Number of cells FSMC FSMD FSME 1 - 3 5 12 19 4 – 6 4 11 18 7 – 9 2 + 1* 9 + 1* 16 + 1* 10 – 12 1+1* 8 + 1* 15 + 1*

* Additional subunit for CCCH resources needed if one System Module and more than 6 cells/10km cell range/2way Rx div.

Example: 1) FSME + FSME / 1 LCG, 12 cells/10km:

Number of subunits = 16 + 16 32 subunits available 2) FSME (LCG1: 6cells/10km) + FSME (LCG2: 6cells/10km)

Number of subunits = 18 + 18 36 subunits available 3) FSMD + FSME / 1 LCG, 12 cells/10km:

(72)

BaseBand resources allocation (2/9)

System Module Rel.2 capacity - number of subunits

Number of cells FSMC FSMD FSME 1 - 3 5 12 19 4 – 6 4 11 18 7 – 9 2 + 1* 9 + 1* 16 + 1* 10 – 12 1+1* 8 + 1* 15 + 1*

* Additional subunit for CCCH resources needed if one System Module and more than 6 cells/10km cell range/2way Rx div.

FSME 6 cells/10km/2way Rx Div (e.g. 2+2+2), 1 LCG

18 subunits

FSME 9 cells/10km/2way Rx Div (e.g. 3+3+3), 1 LCG 17 subunits 1 CCCH subunit needed*

-

=

subunits16 available FSME + FSME

9 cells/10km/2way Rx Div (e.g. 3+3+3), 1 LCG 17 subunits

=>

subunits18 available 17 subunits

=>

subunits34 available

* - 6 cells/10km/2way Rx Div – covered by resources included in SM rel.2 capacity 3 cells/10km/2way Rx Div – 48 Rel.99 CE licenses required

6 cells/10km/2way Rx Div – covered by resources included in Master SM rel.2 capacity 3 cells/10km/2way Rx Div – covered by resources included in Extension SM rel.2 capacity

(73)

BaseBand resources allocation (3/9)

System Module Rel.2 Rel99 CE capacity – number of traffic subunits

HSUPA BTS Processing set Rel99 CE HSUPA thr., users HSDPA thr., users, HSDPA cells HSUPA thr., users Exemplary figure HSDPA thr., users, HSDPA cells 1 subunit

•

Subunits utilized for HSDPA scheduler, HSUPA static resources*, interference cancelation and CCCH processing are allocated based on BTS commissioning and can not be modified without BTS re-commissioning.

•

Rel99 and HSUPA resources are allocated based on traffic need.

•

In case when Rel99 CE licenses and HSUPA licenses covers the same baseband capacity (subunit), overlapped resources can be exchange dynamically between R99 and HSUPA traffic

Rel99 CE

R99 CE licenses HSDPA commissioned resources

* HSUPA static resources might be commissioned by operator (up to 4 HSUPA resource steps –one subunit)

(74)

BaseBand resources allocation (4/9)

System Module Rel.2 Rel99 CE capacity

Table below presents single System Module rel.2 Rel99 CE pure traffic capacity for different cells configuration (10km cell range / 2way Rx div assumed) without HSPA. (1 SU=48 Rel99CE)

Number of cells

FSMC FSMD FSME

RU20 RU40 RU20 RU40 RU20 RU40

1 – 3 180 CE 240 Rel99 CE 396 CE 576 Rel99 CE 612 CE 912 Rel99 CE

10 - 12 144 CE 48 Rel99 CE 360 CE 384 Rel99 CE 576 CE 720 Rel99 CE

Up to 33% capacity gain Up to 46% capacity gain Up to 49% capacity gain FSMC System Module is foreseen for low traffic scenarios (up to 6 cells)

FSMC

FSMD

(75)

BaseBand resources allocation (5/9)

System Module Rel.2 capacity – Impact of HSDPA on subunits allocation

In order to achieve certain HSDPA throughput for HSPA cells appropriate baseband resources need to be allocated for HSDPA scheduler purpose.

HSDPA thr., users, HSDPA cells HSDPA thr., users, HSDPA cells

Number of cells and type of HSPA cells (MIMO/non-MIMO cells Max HSDPA throughput

(commissioned)

0,25 su for HSPA LCG

(76)

BaseBand resources allocation (6/9)

System Module Rel.2 capacity – Impact of HSDPA on subunits allocation

Max HSDPA baseband throughput for System Module rel.2 – reflects the maximum configured HSDPA baseband throughput possible from single System Module rel.2

Up to two HSDPA schedulers can be activated at one System Module Rel.2. Note that HSDPA baseband capacity is common for both schedulers

.

HSDPA_subunits = HSDPA_throughput_subunits + Number_of_LCGs * ¼ of_Subunit

Where: Number_of_LCG = number of HSPA LCGs using System Module rel2 HSPA resources

Maximum HSDPA throughput for System Module Rel.2

HSDPA baseband capacity (HSDPA throughput subunits)

0 Mbps HSDPA schedulers not activated

84 Mbps 2 168 Mbps 3 252 Mbps 4 336 Mbps 5 420 Mbps 6 504 Mbps 7

Note that number and type of HSPA cells (MIMO/non-MIMO) might also impact HSDPA scheduler resources (see HSDPA related slides)

Max HSDPA throughput (commissioned)

(77)

BaseBand resources allocation (7/9)

System Module Rel.2 capacity – HSUPA activated

• HSUPA activation does not consume any baseband resources.

• However for HSUPA users and throughput processing baseband resources (subunits)

needs to be allocated based on current traffic need.

• HSUPA baseband resources allocation is performed in steps – so called HSUPA resource

steps. 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

baseband resources – overlapped resources can be dynamically exchanged between R99

and HSUPA users

(78)

BaseBand resources allocation (8/9)

System Module Rel.2 capacity – HSUPA activated

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

units (PIC pool) needs to be commissioned in order to perform interference cancellation

for mapped 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 3 selected 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

System Module

(79)

BaseBand resources allocation (9/9)

System Module Rel.2 capacity – HSUPA activated

HSPA (f1,f2) R99 (f1,f2) No Frequency mapping to HW / one LCG R99 only (f1,f2) Frequency mapping to HW used / one LCG HSPA (f1) R99 (f1) LCG pooling used HSPA (f2) R99 (f2) LCG1 LCG2 HSPA (f1) R99 (f1,f2) HSPA (f2) R99 (f2)

Fixed BB pooling Flexible BB pooling

Note: DC-HSDPA requires both DC cells in same LCG, served by the same scheduler

HSPA (f1) R99 (f1,f2) HSPA (f2) R99 (f1,f2) HSPA (f1,f2) R99 (f1,f2,f3) HSPA (f3) _{R99 (f1,f2,f3)} Non DC-HSDPA configuration DC-HSDPA capable configuration (f1,f2) HSPA (f1,f2,f3) R99 (f1,f2,f3) R99 only (f1,f2,f3)

(80)

(81)

HSDPA scheduler

SM Rel.2 HSDPA scheduler (1/2)

• One HSDPA scheduler supports:

• Up to 240 HSDPA active users (DC / MIMO / legacy HSDPA users / mixed all HSDPA kind users) • From 1 to 6 cells

• Cells from different LCGs covering baseband capacity of SM with activated HSDPA HSDPA throughput provided by scheduler depends on:

• Activated features

• Number and type of BTS processing sets (# users and throughput) • HSDPA throughput commissioning (BB resources allocation)

There is only one type of HSDPA scheduler with System Module Rel.2

HSDPA schedulers available for HW Rel.1 same as in RU10/RU20 Up to 2 HSDPA schedulers are supported with one SM Rel.2

(82)

HSDPA scheduler

SM Rel.2 HSDPA scheduler (2/2)

Operator can activate HSDPA scheduler by HSDPA throughput step commissioning. • The following HSDPA throughput step values are available: from 0 up to 35 • Each step refers to 7,2Mbps (e.g. 1- 7,2Mbps; 2- 14,4Mbps, etc)

• HSDPA throughput commissioning is optional and if not commissioned, BTS will allocate HSDPA throughput based on the default rules (please see next slide)

HSDPA throughput steps Maximum throughput for HSDPA scheduler

0 HSDPA schedulers not activated 1, 2, 3, 4, 5, 6 42 Mbps 7, 8, 9, 10, 11, 12 84 Mbps 13, 14, 15, 16, 17, 18 126 Mbps 19, 20, 21, 22, 23, 24 168 Mbps 25, 26, 27, 28, 29, 30 210 Mbps 31,32, 33, 34, 35 252 Mbps

Note that table presents max baseband throughput and does not take into

consideration any limitations e.g. Iub configuration etc.

HSDPA_scheduler_throughput =

Min {HSDPA_throughput_step * 7.2 Mbps ; Maximum throughput for HSDPA scheduler}

Where:

HSDPA_throughput_step = commissioned scheduler throughput Maximum throughput for HSDPA=maximum throughput referred in Mbps for corresponding HSDPA throughput step from above

The max HSDPA scheduler BB throughput can be calculated with formula* :

* Note that HSDPA licensed throughput might limit HSDPA commissioned throughput. I m p a c t o n B B u t i l i z a t i o n

(83)

HSDPA scheduler

Minimum allocation rule

•To assure optimal HSDPA performance BTS checks whether resources allocated for HSDPA are appropriate for BTS configuration

•In case when commissioned throughput is too low in reference to number of HSDPA cells, BTS prevents to allocate lower HSDPA throughput below level specified by minimum allocation rule

Tables below presents minimum allocation rule for HSDPA scheduler for MIMO and non-MIMO cells

Non-MIMO cells Minimum HSDPA throughput

1 – 3 42 Mbps 4 – 6 84 Mbps

MIMO cells per scheduler Minimum HSDPA throughput per scheduler 1 – 3 84 Mbps 4 – 6 168 Mbps Minimum allocation rule for HSDPA scheduler for

non-MIMO cells

Minimum allocation rule for HSDPA scheduler for MIMO cells

Number and type of HSPA cells

(84)

Example: 1 SM rel.2, Scheduler ID 1 = 2, Scheduler ID 2 = 5 Scheduler ID1 = 2 x 7,2 = 14,4 Mbps Scheduler ID2 = 5 x 14,4 = 36 Mbps

HSDPA scheduler

Example

HSDPA throughput steps Maximum throughput for HSDPA scheduler

0 HSDPA schedulers not activated 1, 2, 3, 4, 5, 6 42 Mbps 7, 8, 9, 10, 11, 12 84 Mbps 13, 14, 15, 16, 17, 18 126 Mbps 19, 20, 21, 22, 23, 24 168 Mbps 25, 26, 27, 28, 29, 30 210 Mbps 31,32, 33, 34, 35 252 Mbps Master SM rel.2 HSDPA_scheduler_throughput =

(85)

HSDPA scheduler

HSDPA baseband requirements

•HSDPA schedulers do not consume Rel99 CE licenses but depending on commissioned HSDPA throughput HSDPA schedulers would limit the number available subunits.

•Table below presents combined maximum throughput for HSDPA schedulers located at given System Module Rel.2 and corresponding HSDPA baseband capacity utilization.

Combined Maximum throughput for HSDPA schedulers located at System

Module Rel.2

HSDPA baseband capacity reservation (number of subunits)

0 Mbps HSDPA schedulers not activated

42 Mbps 2 84 Mbps 2 126 Mbps 3 168 Mbps 3 210 Mbps 4 252 Mbps 4 294 Mbps 5 336 Mbps 5 378 Mbps 6 420Mbps 6 462 Mbps 7 504 Mbps 7

(86)

HSDPA scheduler

HSDPA - Formula to calculate HSDPA Subunit Consumption

• Baseband capacity (subunits) required by HSDPA can be calculated according to the formula below:

Subunits_for_HSDPA = Max { (Round up ((2 * MIMO_cells + non-MIMO_cells) / 6) + 1) ; subunits_for_HSDPA_throughput) + Number_of_LCGs * 0,25

Where:

 MIMO_cells = number of HSDPA cells with MIMO activated

 non-MIMO_cells = number of HSDPA cells without MIMO

 Subunits_for_HSDPA_throughput = number of subunits based on commissioning (see below)

(87)

HSDPA scheduler

HSDPA - Formula to calculate HSDPA Subunit Consumption

Example: - 3 + 3 + 3 configuration , Rel’2 SM & RF Modules, 1 LCG

- HSDPA in f1 and f2, MIMO on f1, Rel’99 on f3, 84 Mbps HSDPA throughput

MIMO_cells = 3 (MIMO is on f1)

non-MIMO_cells = 3 (cells in f2 are HSDPA non MIMO cells) Subunits_for_HSDPA_throughput = 2 subunits

Number_of_LCGs = 1 Local Cell Group

Subunits_for_HSDPA = Max ( (Roundup ((2 * ? + ?) / 6) + 1 ) ; ?) + ? * 0,25

= Max (? ; ?) + 0,25 = ? + 0,25 = ?

Subunits_for_HSDPA = Max ( (Round up ((2 * MIMO_cells + non-MIMO_cells) / 6) + 1) ; subunits_for_HSDPA_throughput ) + Number_of_LCGs * 0,25

(88)

HSDPA scheduler

HSDPA - Formula to calculate HSDPA Subunit Consumption

Example: - 3 + 3 + 3 configuration , Rel’2 SM & RF Modules, 1 LCG

- HSDPA in f1 and f2, MIMO on f1, Rel’99 on f3, 84 Mbps HSDPA throughput

MIMO_cells = 3 (MIMO is on f1)

non-MIMO_cells = 6 (cells in f2 and f3)

Subunits_for_HSDPA_throughput = 2 subunits Number_of_LCGs = 1 Local Cell Group

Subunits_for_HSDPA = Max ( (Roundup ((2 * 3 + 6) / 6) + 1 ) ; 2) + 1 * 0,25

= Max (3 ; 2) + 0,25 = 3 + 0,25 = 3,25 Subunits_for_HSDPA = Max ( (Round up ((2 * MIMO_cells + non-MIMO_cells) / 6) + 1) ;

(89)

HSDPA scheduler

Summary

System Module Rel.2 HSDPA scheduler description

System Module Rel.2 description Max. number of Active Users per

HSDPA scheduler

Max number of cells assign to

HSDPA scheduler Max scheduler throughput

240 6 252 Mbps

Max number of HSDPA schedulers per System

Module Rel.2

Max number of HSDPA Active Users per System

Module Rel.2

Max number of HSDPA cells per System

Module Rel.2

Max HSDPA peak throughput per System

Module Rel.2

2 480 12 (6 cell per scheduler) 504 Mbps (252 Mbps per scheduler)

(90)

(91)

HSUPA baseband resources allocation in RU40

HSUPA Processing Set in RU40

• In RU40 HSUPA Processing Set license allows to reach up to 5.8Mbps and 24 users simultaneously • The HW reservation inside System Module is not reflecting the number of HSUPA PS licenses

• 1 HSUPA Processing Set <> 1,5 Subunit

• Appropriate amount of HSUPA resource steps is reserved to fulfill the throughput and users requirements from available number of HSUPA PS licenses

• BB reservation granularity is 1 resource step (0,25 subunit from System Module rel.2)

HSDPA thr., users,

HSDPA cells HSDPA thr., users,_{HSDPA cells} HSUPA Subunit HSUPA licensed capacity HSUPA thr., users BB capacity HSUPA BTS Processing sets HSUPA thr., users 1 Subunit

(92)

HSUPA in RU40

2 HSUPA schedulers per one LCG

• In RU40 with System Module Rel.2, one HSUPA scheduler can support up to 240 HSUPA users from 1 to 12 cells.

• Up to two HSUPA schedulers can be allocated per single LCG with two System Module rel.2 and frequency layers mapping to HW (note that frequency mapping to HW is possible only in one LCG scenario)

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

LCG1

f1 f2 480 HSUPA users per LCG 240 HSUPA users per Extension System Module 240 HSUPA users per Master System Module

(93)

HSUPA resources allocation

System Module Rel.2

•

If licensed R99 and HSUPA baseband resources (allowed with the available HSUPA BTS processing sets and Rel99 CE licenses) exceeds System Module rel.2 capacity, overlapping baseband resources can be

dynamically exchange between R99 and HSUPA users.

•

One HSUPA BTS Processing Set license can be utilized by R99 users (48Rel99 CE) even without R99 CE licenses.

•

Other HSUPA resources can be also dynamic, but only if they are overlapped by Rel99 CE licenses

Can be utilized by R99 users

Rel99 CE licenses

Can be utilized by R99 users

BB resources

HSUPA BTS Processing sets 48CE (dynamic) 48CE (dynamic) HSUPA BTS Processing set HSUPA BTS Processing set