Baseband Dimensioning_RU40 (1).pdf
Short Description
Download Baseband Dimensioning_RU40 (1).pdf...
Description
Baseband Dimensioning
Module Objectives
At the end of the module you will be able to: • Recall the baseband capacity of the Flexi Multiradio BTS (Flexi System Module rel.3 and Rel2) and Flexi Lite BTS (optional material) • Perform baseband allocation/dimensioning allocation/dimensioning rules for R99, HSDPA & HSUPA traffic
Module Objectives
At the end of the module you will be able to: • Recall the baseband capacity of the Flexi Multiradio BTS (Flexi System Module rel.3 and Rel2) and Flexi Lite BTS (optional material) • Perform baseband allocation/dimensioning allocation/dimensioning rules for R99, HSDPA & HSUPA traffic
Baseband Dimensioning • RU40 Licensing Aspects • Rel99 CE license • HSDPA BTS Processing Sets license • HSUPA BTS Processing Sets license • CCCH Processing Sets license
• Baseband Dimensioning Essentials • RU40 System Modules capacity • Local Cells Grouping • Frequency based pooling • Sector based pooling • Frequency mapping to HW
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
RU40 Licensing aspects
Licensing aspects (1/8) General information RU40 Licensing aspects
• • •
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
HSUPA Processing sets
HSDPA users / throughput – HSDPA BTS Processing Sets
Rel99 CE
HSUPA users / throughput – HSUPA BTS Processing Sets
HSDPA Processing sets
R99 (DCH, A-DCH) traffic – Rel99 CE licenses SM rel.2
SM rel.3
Licensing aspects (2/8) Rel99 CE licenses 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)
Licensing aspects (3/8) Rel99 CE licenses 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
Licensing aspects (4/8) HSDPA BTS processing set 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)
Licensing aspects (5/8) HSDPA BTS processing set 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 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
Note that HSDPA Processing Set 1 is not taken into
Licensing aspects (6/8) HSUPA BTS processing set 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
Licensing aspects (7/8) HSPA BTS processing set (RU40) – summary HSUPA and HSDPA BTS processing sets
• • • •
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.
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.
Baseband dimensioning essentials
Baseband dimensioning process
Amount of cells Required features (e.g. 4 Rx Div, Interference cancellation, DC HSDPA)
Amount of HSPA users and HSPA throughput
I n p u t p a r a m e t e r s
CCCH processing resources HSDPA scheduler resources
Start
HSUPA scheduler static resources
BTS configuration ( SM/RF module HW type)
DCH/ADCH/SRB resources
B B a l l o c a t i o n
HSUPA scheduler resources How many LCGs are required ? How many cells per LCG ? LCG pooling type ? (Fixed/Flexible/Sector based)
L C G p o o l i n g
Select next bigger configuration or reconfigure Local Cell Grouping
No
Traffic demand fulfilled ? Yes
End
Baseband allocation and capacity license dimensioning process BB allocation
CCCH resources • Commissioned HSDPA thr. (SM rel.2) • LCG configuration type (SM rel.3) • Amount of MIMO/nonMIMO cells • Commissioned HSUPA thr and users (HSUPA scheduler static resources) • Amount of PIC pools
HSDPA resources
Rel99 CE licenses / CCCH Processing Sets
HSDPA Processing Sets (amount and type)
Static HSUPA resources
DCH/ADCH/SRB resources • Amount of HSUPA users • HSUPA throughput • Amount of activated HSUPA schedulers
Capacity License dimensioning
HSUPA scheduler resources
• Amount of cells • Req. cell range • Rx Div type • Amount of HSDPA users • HSDPA throughput • Amount of activated HSDPA schedulers
HSUPA Processing Sets (amount)
Rel99 CE licenses HSUPA Processing Sets (amount)
• Amount and type of: - R99 users - HSDPA users (ADCH/SRB)
Local Cell Grouping
Local Cell Grouping LCG description • 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 Operator RAN (MORAN) case. • When Local Cell Grouping is done – done – available available BTS capacity is split among LCG according to BTS commissioning settings. Baseband allocation to LCG 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 4way 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: • Frequency layer based • Sector based L C G 1
LCG2
LCG3
LCG4
Frequency based pooling
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. LCG1:f1 LCG2:f2 RF modules LCG2 System Module
LCG1
Exemplary BTS configuration with flexible baseband pooling
Frequency based pooling (2/3) General information Fixed BB pooling (e.g. RF rel.1 used)
LCG1
LCG2
SM rel.2
SM rel.2
Flexible BB pooling (pure HW rel.2/rel.3 configuration)
LCG1
SM rel.2
LCG1
LCG2
SM rel.2
Commissioning parameter Access baseband capacity is used to define LCGs baseband capacity
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) DC-HSDPA possible only when both DC carriers belong to same LCG .
Sector based pooling
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)
f1 f2 f3 f4
Example of Frequency based pooling Examples of Sector based pooling
RF modules
System Modules
RF modules LCG2 LCG1
System Modules
LCG2 LCG1
Effect of using sector based pooling might be the same as using frequency based pooling
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) 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 Module rel.3 up to 2 LCGs can be created. D C H S D P A
LCG1
FSM rel.2
LCG2
FSM rel.2
FSM rel.2 + FSM rel.2 (sector based polling)
LCG2
FSM rel.3
FSM rel.3 (sector based polling)
Benefits/constrains:
• • • •
HSPA on both System Modules with 2 LCGs More HSUPA schedulers (one HSUPA scheduler per LCG) and baseband capacity for HSPA traffic DC-HSDPA possible (DC sectors split between LCGs) Increase soft handover factor
Frequency mapping to HW
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 is mapped to a System Module, 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 frequency layer . 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 Module.
•
With Frequency mapping to HW it is possible to have HSPA on both System Modules with one LCG.
200/240 HSUPA users per Extension System Module
LCG1 400/480 HSUPA users per LCG
f1 f2
200/240 HSUPA users per Master System Module
Frequency mapping to HW can be used only with one LCG scenario
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
MSM
HSUPA (f1,f2)
HSDPA (f1,f2)
A-DCH (f1,f2)
DCH (f1,f2,f3)
ESM
HSUPA (f3)
HSDPA (f3)
A-DCH (f3)
DCH (f1, f2,f3)
MSM
ESM
R99 traffic of all carriers served
f1 f2 f3
RU40 Baseband Dimensioning Flexi System Module rel.3 Baseband dimensioning
System Module rel.3 capacity
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 subunits
Number of cells
FSMF without capacity extension submodul submodules es (subunits)
1 – 6 – 6
5,5
7 –12 –12
5 + 0,5
Table assumes 10km cell range and 2way Rx Div
•
Additional resources resources for CCCH processing needed needed if one System System Module and more than 6 cells/10km cell range/2way Rx div. div.
Available Available resources resources (subunits) (subunits) can can be used used for CCCH processing, processing, HSDP HSDPA A schedulers schedulers processing, HSUPA HSUPA users and thr. processing, R99 users processing and interference cancellation processing
•
Please note that each System Module rel.3 contains CCCH processing resources required for ‘Basic Configurations’ (e.g. 6 cells/10km or 3cells/20km – 3cells/20km – 2way 2way Rx Div) included in the System Module rel.3 capacity
System Module rel.3 capacity(2/3) System Module Rel.3 capacity - number of subunits
• • •
One type of Extension submodule available for WCDMA: FBBA Extension submodule are used to extend System Module capacity Up to 2 Extension submodules can be used to extend capacity of single System Module rel.3
Expansion Submodule
Available Subunits
FBBA
6
2x Capacity expansion submodule (FBBA -> WCDMA)
LCG Configurations
LCG Configurations (1/14) LCG configuration types System Module rel.3 LCG configuration
•
System Module rel.3 LCG might be commissioned to one out of the three configurations:
•
Rel99 only (up to 12 cells)
• •
Small HSPA configuration (up to 6 cells)
• •
Support of UMTS Rel.99 services, no support for HSPA
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)
LCG configuration type might be commissioned using HSPA setting parameter
Note that LCG configuration type commissioning is optional. By default Normal HSPA configuration is assumed
LCG Configurations (2/14) LCG configuration types System Module rel.3 LCG configuration
HSDPA scheduler BB resources allocation
LCG configuration type
Optional CCCH processing baseband resources for additional CCCH requirements (e.g. higher cell range)
Exemplary configuration - BTS with 3 different LCG types
LCG1: Rel99 only configuration
LCG2: Small HSPA configuration
LCG3: Normal HSPA configuration
Rel99 only (up to 12 cells)
HSPA + R99 (up to 6 cells)
HSPA + R99 (up to 12 cells)
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
LCG Configurations (3/14) LCG configuration types HSPA LCG configuration (Small HSPA or Normal HSPA) impact on traffic capacity
LCG capacity (e.g. LCG1: FSMF – 5,5 subunits)
LCG: Rel99 only configuration
LCG: Small HSPA configuration LCG: Normal HSPA configuration
HSDPA scheduler resources
HSDPA_scheduler_resources =
(1x HSDPA scheduler)
max { (Cells_factor / 2) - 0,5 ; Min_HSDPA_resources } + 0,125 HSDPA scheduler resources (2x HSDPA schedulers)
where: Cells_factor = Roundup { [ RoundUp(non-MIMO cells/3) + MIMO cells] / 2 } LCG configuration
(Min_HSDPA_resources)
Small
0,5
Normal
1
LCG Configurations (4/14) LCG configuration types – impact on capacity HSPA LCG configuration (Small HSPA or Normal HSPA) impact on traffic capacity
LCG configuration: Small HSPA or Normal HSPA configuration
HSDPA scheduler Resources (subunits) Additional CCCH processing baseband resources
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.
LCG Configurations (5/14) LCG configuration types – impact on capacity HSPA LCG configuration (Small HSPA or Normal HSPA) impact on traffic capacity
LCG1 LCG2
LCG1: Small HSPA configuration
CCCH processing resources included in FSMF SM capacity
LCG2: Normal HSPA configuration
0,5 su (1 x CCCH Processing Set LK)
HSDPA scheduler resources Optional CCCH processing BB resources
HSDPA scheduler resources Optional CCCH processing BB resources
CCCH Processing Sets license(s) required to use optional CCCH processing baseband resources included in HSDPA scheduler capacity
LCG Configurations (6/14) LCG configuration types – impact on capacity HSPA LCG configuration (Small HSPA or Normal HSPA) impact on traffic 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
Max number of supported cells
Max number of HSPA cells
LCG configuration
(Min_HSDPA_resources)
Rel99 only
12
0
Small
0,5
Small
6
6
Normal
1
Normal
12
12
Number of additional CCCH processing pools available with Small and Normal HSPA configuration:
#_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 Configurations (7/14) LCG configuration types – impact on capacity (non-MIMO cells) HSPA LCG configuration (Small HSPA or Normal HSPA) impact on traffic capacity 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)
Normal
Normal
Up to 6 cells
Up to 12 cells
1,125 (HSDPA scheduler) 1,125 (HSDPA scheduler)
0,5 (CCCH) + 0,625 (HSDPA scheduler) = 1,125 0,5 (CCCH) + 1,125 (HSDPA scheduler) = 1,625 0,5 (CCCH) + 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)
1 x CCCH Processing Sets required
2 x CCCH Processing Sets required
LCG Configurations (8/14) LCG configuration types – impact on capacity (MIMO cells) HSPA LCG configuration (Small HSPA or Normal HSPA) impact on traffic capacity 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*)
Small
5 - 6 MIMO cells
1,125 (HSDPA scheduler*)
0,5 (CCCH) + 1,125 (HSDPA scheduler*)
Normal
Up to 6 MIMO cells
1,125 (HSDPA scheduler*)
0,5 (CCCH) + 1,125 (HSDPA scheduler*)
Normal
7 – 8 MIMO cells
1,625 (HSDPA scheduler*)
0,5 (CCCH) + 1,625 (HSDPA scheduler*)
9 - 10 MIMO cells
2,125 (HSDPA scheduler*)
Normal
Normal
10 - 12 MIMO cells
2,625 (HSDPA scheduler*)
= 1,125
= 1,625
= 1,625
= 2,125 0,5 (CCCH) + 2,125 (HSDPA scheduler + optional CCCH) = 2,625 0,5 (CCCH) + 2,625 (HSDPA scheduler + optional CCCH) = 3,125
1 x CCCH Processing Sets required
2 x CCCH Processing Sets required
LCG Configurations (9/14) LCG configuration types – Rel99 only System Module rel.3 LCG configuration – Rel99 only
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
Number of cells
FSMF
1-6 cells
5½ SU
7-12 cells
5 +½* SU
Table assumes 10km cell range / 2way Rx Div / 1 LCG
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
LCG Configurations (10/14) LCG configuration types – Rel99 only System Module rel.3 LCG configuration – Rel99 only
Number of cells
Core System Module
1-6 cells FSMF 7-12 cells
Expansion Submodule
#R99Subunits
-
5½
FBBA
11½
FBBA +FBBA
17½
-
5+½
FBBA
11 + ½
FBBA +FBBA
17 + ½
Table assumes 10km cell range and 2way Rx Div
Note: 1x CCCH Processing Set license for more than 6 cells/10km are required (CCCH)
LCG Configurations (11/14) LCG configuration types – Small HSPA System Module rel.3 LCG configuration – Small HSPA
Number of cells
FSMF
1-6 cells
4 7/8 SU
CCCH included in SM rel.3 capacity
Table assumes 10km cell range and 2way Rx Div
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 Up to 160 active users
LCG Configurations (12/14) LCG configuration types – Small HSPA System Module rel.3 LCG configuration – small HSPA
Number of cells Up to 6 HSPA cells
Core Module
Extension Submodule
Subunits
-
4 7/8 SU
FBBA
10 7/8 SU
FBBA +FBBA
16 7/8 SU
FSMF
Table assumes 10km cell range and 2way Rx Div
LCG Configurations (13/14) LCG configuration types – Normal HSPA System Module rel.3 LCG configuration – Normal HSPA
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
Number of cells
FSMF
1-6 cells
4 3/8 SU
7-12 cells
4 3/8 SU ???
Table assumes 10km cell range and 2way Rx Div
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 Up to 240 active users
LCG Configurations (14/14) LCG configuration types – Normal HSPA System Module rel.3 LCG configuration – Normal HSPA
Number of cells Up to 12 HSPA cells
Core Module
FSMF
Table assumes 10km cell range and 2way Rx Div
Extension Submodule
Subunits
-
4 3/8 SU
FBBA
10 3/8 SU
FBBA +FBBA
16 3/8 SU
HSDPA Dimensioning
HSDPA scheduler (1/2) HSDPA scheduler details HSDPA scheduler
• •
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
Combined Maximum throughput for HSDPA schedulers located at System Module Rel.2
HSDPA baseband capacity reservation (number of subunits)
0 Mbps 42 Mbps 84 Mbps 126 Mbps 168 Mbps 210 Mbps 252 Mbps 294 Mbps 336 Mbps 378 Mbps 420Mbps 462 Mbps 504 Mbps
HSDPA schedulers not activated 2 2 3 3 4 4 5 5 6 6 7 7
Baseband resources required by HSDPA scheduler (System Module rel.2)
Up to 252Mbps / scheduler 0Mbpsca pacity gain
Additional baseband resources not required by HSDPA scheduler (System Module rel.3)*
* Only A-DCH/SRB CE resources needed for HSDPA users (UL:R99
HSDPA scheduler (2/2) Commissioning the Maximum HSDPA Throughput •
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 throughput steps
HSDPA throughput Mbps
HSDPA throughput steps (continued)
HSDPA throughput Mbps
1
7.2
8
57.6
2
14.4
…
…
3
21.6
13
93.6
14
100.8
… 6
43.2
…
…
7
50.4
35
252
• 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
CCCH and R99 Dimensioning
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:
• • • • •
•
DL
Number of cells
1 x P-SCH
Cell range
1 x S-SCH
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
1 x P-CCPCH 1 x P-CPICH 1 x PICH 1 x AICH 3 x S-SCCPCH
UL PRACH
CCCH processing resources allocation CCCH baseband resources allocation Basic configurations for 1 LCG (e.g. 6cell/10km, 3 cells/20km
1) CCCH processing resources included in SM rel.3 capacity (available for 1 LCG). Additional LCG requires 1 CCCH pool (0,5 subunit)
More CCCH processing resources needed ( e.g. high number of cells or higher cell range) ?
CCCH processing baseband capacity
CCCH processing license capacity
One CCCH pool included in FSM rel.3
License not needed
One CCCH pool = 0.5 subunit No
e.g. second LCG
License needed (CCCH Processing Set(s))
Yes
Small HSPA
Normal HSPA
Still more CCCH processing resources needed ( e.g. high number of cells/higher cell range) or R99 Only LCG config.? Small HSPA
X amount of CCCH pool(s) included in LCG configuration resources
2) LCG configuration type (Small HSPA and Normal HSPA configuration only)
License needed (CCCH Processing Set(s))
No
Yes Normal HSPA
1 subunit CCCH pool
3) LCG capacity resources allocation for CCCH processing
One CCCH pool = 0,5 subunit
License needed (CCCH Processing Set(s))
CCCH processing resources allocation Example 1 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
Note that CCCH processing resources are LCG specific
LCG 2
FSMF + FBBA
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 LCG2 – 6cells/20km cell/2way Rx Div -> 2 CCCH Processing Set licenses needed -> 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
Number of additional CCCH processing pools available with Small HSPA configuration: #_CCCH_available_pools = max { Min_HSDPA_resources ; (Cells_factor / 2) – 0,5 } / 0,5 = max {0,5 ; 1 / 2 - 0,5} / 0,5 = 1 Cells_factor = Roundup { [ RoundUp(non-MIMO cells/3) + MIMO cells] / 2 } = 1 Min_HSDPA_resources = 0,5
CCCH processing resources allocation Example 2 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
Note that CCCH processing resources are LCG specific
LCG 2
FSMF + FBBA LCG1 – 6cells/20km cell/2way Rx Div -> 1 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 LCG2 – 6cells/20km cell/2way Rx Div -> 2 CCCH Processing Set licenses needed -> 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
Number of additional CCCH processing pools available with Normal HSPA configuration (LCG2): #_CCCH_available_pools = max { Min_HSDPA_resources ; (Cells_factor / 2) – 0,5 } / 0,5 = max {1 ; 1 / 2 - 0,5} / 0,5 =2 Cells_factor = Roundup { [ RoundUp(non-MIMO cells/3) + MIMO cells] / 2 } = 1 Min_HSDPA_resources = 1
1 CCCH pool (included in HSDPA scheduler resources) still available
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: # _ of _ cells
(Cell Rangei * # of Signature si * Rx) 480 i 1
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 =
View more...
Comments
