For internal use
Unique document identifier (ID) / Version number / Life cycle status
1
© Nokia Siemens Networks 2013
Disclaimer
This slide set shall not be 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.
For internal use
Unique document identifier (ID) / Version number / Life cycle status
2
© Nokia Siemens Networks 2013
Baseband Dimensioning fundamentals
Table of Contents
3
1
Local Cells Grouping
6
R99 resources allocation
2
Frequency BB pooling
7
HSUPA Processing Sets allocation
3
Sector based pooling
8
HSDPA license distribution
4
Frequency Mapping to HW
9
HSDPA scheduler characteristic
5
HSPA resources allocation
10
Tcell grouping
For internal use
© Nokia Siemens Networks 2013
Local Cell Grouping (BB pooling)
For internal use
Unique document identifier (ID) / Version number / Life cycle status
4
© Nokia Siemens Networks 2013
Local Cell Grouping
Main Menu
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 – 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 4-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:
– Frequency layer based
– Sector based
L
C
G
1
5
For internal use
© Nokia Siemens Networks 2013
LCG2
LCG3
LCG4
Exemplary LCG configuration - Frequency
layer based pooling used (up to 4 LCGs)
Frequency BB pooling
For internal use
Unique document identifier (ID) / Version number / Life cycle status
6
© Nokia Siemens Networks 2013
Frequency BB pooling
Main Menu
Description
• 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
Exemplary BTS
configuration with flexible
baseband pooling
RF
modules
LCG2
System Module
7
For internal use
© Nokia Siemens Networks 2013
LCG1
Frequency BB pooling
Main Menu
Description
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
LCG2
LCG1
SM rel.2
Commissioning parameter Access baseband capacity is used to define LCGs baseband capacity
8
For internal use
© Nokia Siemens Networks 2013
MBB CS Network Engineering/ Krzysztof Mertas
Frequency BB pooling
Main Menu
Requirements
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.
9
For internal use
© Nokia Siemens Networks 2013
Sector based pooling
For internal use
Unique document identifier (ID) / Version number / Life cycle status
10
© Nokia Siemens Networks 2013
Sector based pooling
Main Menu
Description
•
In RU30EP2, 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
RF
modules
System Modules
11
Examples of Sector based pooling
RF
modules
LCG2
For internal use
LCG1
© Nokia Siemens Networks 2013
LCG2
System Modules
LCG1
Effect of using sector based
pooling might be the same
as using frequency based
pooling
Sector based pooling
Main Menu
Requirements
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.
DC HSDPA
LCG1
FSM rel.2
LCG2
FSM rel.2
FSM rel.2 + FSM rel.2
(sector based polling)
Benefits/constrains:
LCG2
FSM rel.3
FSM rel.3
(sector based polling)
• 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
12
For internal use
© Nokia Siemens Networks 2013
Frequency Mapping to HW essentials
For internal use
Unique document identifier (ID) / Version number / Life cycle status
13
© Nokia Siemens Networks 2013
Frequency mapping to HW
Main Menu
Description
• 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
f1
400/480 HSUPA users per LCG
f2
200/240 HSUPA
users per Master
System Module
14
For internal use
© Nokia Siemens Networks 2013
Frequency mapping to HW can be used only with one LCG scenario
Frequency mapping to HW
Main Menu
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
15
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)
For internal use
© Nokia Siemens Networks 2013
Powerpoint – template, gallery and tutorial / August 2009
MSM
ESM
R99 traffic of all
carriers served
on both FSMEs
f1
f2
f3
HSPA resources allocation
For internal use
Unique document identifier (ID) / Version number / Life cycle status
16
© Nokia Siemens Networks 2013
HSPA resources allocation
Main Menu
Description
HSPA (f1,f2)
Note: DC-HSDPA
requires both DC cells in
same LCG, served by
the same scheduler
LCG1
HSPA (f1)
LCG2
HSPA (f2)
HSPA (f1,f2,f3) R99 (f1,f2,f3)
R99 only (f1,f2)
R99 only (f1,f2,f3)
Non DC-HSDPA
configuration
DC-HSDPA capable
configuration (f1,f2)
HSPA (f1)
R99 (f1,f2)
HSPA (f1,f2) R99 (f1,f2,f3)
HSPA (f2)
R99 (f1,f2)
HSPA (f3)
R99 (f1)
HSPA (f1)
No Frequency
mapping to HW / one
LCG
Frequency mapping to
HW used / one LCG
R99 (f1,f2,f3)
R99 (f1,f2)
LCG pooling used
R99 (f2)
Fixed BB pooling
17
R99 (f1,f2)
For internal use
© Nokia Siemens Networks 2013
HSPA (f2)
R99 (f2)
Flexible BB pooling
(pure HW rel.2 needed)
HSPA resources allocation
Main Menu
Description
HSPA call (UL:R99, DL: HSDPA)
DCH/A-DCH
HSDPA
SM rel.2
DCH/A-DCH
Exemplary BTS
configuration:
- SM rel.2 + SM rel.2, 1LCG,
Frequency mapping to HW
not used
SM rel.2
• HSDPA service (UL:R99, DL HSDPA) requires the following baseband resources:
• HSDPA scheduler
• SRB resources in DL (1 Rel99 CE per each user)
• A-DCH resources in UL (X Rel99 CE per each user depending on bearer rate)
• All baseband resources for single HSDPA call are located in the same System Module.
18
For internal use
© Nokia Siemens Networks 2013
HSPA resources allocation
Main Menu
Description
HSPA call (UL:HSUPA, DL: HSDPA)
R99
HSDPA
SM rel.2
HSUPA
R99
Exemplary BTS
configuration:
- SM rel.2 + SM rel.2, 1LCG,
Frequency mapping to HW
not used
SM rel.2
• HSUPA service (UL:HSUPA, DL HSDPA) requires the following baseband resources:
• HSUPA scheduler
• HSDPA scheduler
• All baseband resources for single HSUPA call are located in the same System Module.
• HSUPA scheduler can allocate only baseband resources inside single System Module (max 15 subunits). If
HSUPA is needed on both SMs then 2 HSUPA schedulers must be activated (Frequency mapping to HW or Local Cell
Grouping to be used)
19
For internal use
© Nokia Siemens Networks 2013
HSPA resources allocation
Main Menu
Description
MiltiRAB call -> HSPA + AMR
HSPA call (UL:R99,
DL: HSDPA)
HSPA call (UL:HSUPA,
DL: HSDPA)
AMR call
AMR call
R99
HSDPA
SM rel.2
HSPA call
(UL:HSUPA,
DL: HSDPA)
HSPA call
(UL:R99,
DL:
HSDPA)
20
Exemplary BTS
configuration:
- SM rel.2 + SM rel.2, 1LCG,
Frequency mapping to HW
not used
HSUPA
R99
SM rel.2
- 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 on HSUPA resources) as HSPA
non-FDPCH user
- AMR call needs to be served at the same System Module as HSDPA
- Additional R99 resources (UL/DL) needs to be allocated for AMR call (1 Rel.99 CE license needed)
For internal use
© Nokia Siemens Networks 2013
R99 resources allocation
For internal use
Unique document identifier (ID) / Version number / Life cycle status
21
© Nokia Siemens Networks 2013
R99 resources allocation
Main Menu
description
• R99 baseband resources are allocated at HSPA System Module unless Frequency mapping to HW is used.
• With Frequency mapping to HW R99 carrier can be mapped to non-HSPA System Module
1 LCG
1st priority
R99
HSDPA
2nd priority
HSUPA
R99
R99 baseband
resources allocation –
1 LCG, HSPA
mapping to HW not
used
SM rel.2
SM rel.2
If amount of available resources on HSPA System Module reach threshold, new R99 users
can be reallocated to non-HSPA System Module
Not that CCCH processing resources are allocated at the same System Module as HSPA resources.
When Frequency mapping to HW is used then CCCH processing resources are on both System Modules
according to mapped cells.
22
For internal use
© Nokia Siemens Networks 2013
HSUPA Processing Sets distribution
For internal use
Unique document identifier (ID) / Version number / Life cycle status
23
© Nokia Siemens Networks 2013
HSUPA license throughput distribution
Main Menu
description
• Available HSUPA BTS processing set resources needs to be distributed among HSUPA schedulers
•
If HSUPA scheduler is present in both System Modules (same LCG), in this case BTS will allocate HSUPA
licenses proportionally to baseband capacity for traffic use of each System Module, with BTS processing set
granularity (see next slide).
• If Baseband pooling is used then BTS will divide HSUPA licenses between LCG’s according to
commissioned share (shareOfHSUPALicense). 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.
24
For internal use
© Nokia Siemens Networks 2013
HSUPA license throughput distribution
Main Menu
1 LCG scenario (Frequency mapping to HW used)
1 LCG
Total # of HSUPA Processing Sets
# HSUPA Processing Sets
# HSUPA Processing Sets
HSUPA Sch.1
HSUPA Sch.2
SM rel.2
SM rel.2
Baseband capacity for
traffic use – SM capacity
after CCCH, HSDPA,
PIC pool allocation
• The following principles are used to distribute HSUPA Processing Sets among 2 HSUPA schedulers (1 LCG):
HSUPA_SM1 = RoundDown { SM_1_subunits / (SM_1_subunits + SM_2_subunits) * Total_#_HSUPA_Processing_Sets }
HSUPA_SM2 = RoundDown { SM_2_subunits / (SM_1_subunits + SM_2_subunits) * Total_#_HSUPA_Processing_Sets}
where: SM_1_subunits – SM_1 amount of subunit for traffic use (after HSDPA scheduler(s), PIC and CCCH subunits allocation)
SM_2_subunits – SM_2 amount of subunit for traffic use (after HSDPA scheduler(s), PIC and CCCH subunits allocation)
Total_#_HSUPA_Processing Sets – total amount of available HSUPA Processing Sets
• The remaining licensed HSUPA Processing Set (if any) will be assigned to scheduler with lower number of HSUPA
Processing Sets. If both schedulers have the same amount of HSUPA Processing Sets, then remaining HSUPA
Processing Set will be assigned to the scheduler located at Master System Module.
25
For internal use
© Nokia Siemens Networks 2013
HSDPA license (users and throughput)
distribution
For internal use
Unique document identifier (ID) / Version number / Life cycle status
26
© Nokia Siemens Networks 2013
HSDPA license throughput distribution
Main Menu
description
• Available HSDPA BTS processing set resources are distributed among HSDPA schedulers.
• Different rules are used for distribution of active users and throughput.
27
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
For internal use
© Nokia Siemens Networks 2013
HSDPA license throughput distribution
Main Menu
HSDPA users distribution
HSDPA active users
• Total licensed HSDPA users is controlled on BTS level and it can be divided between LCGs according to
commissioned shares.
•
Commissioning share option (HSDPAusershare) defines the guaranteed HSDPA user capacity for each LCG.
•
If commissioning is not done then user amount will be equally distributed among LCGs.
For example:
– 1 HSDPA BTS Processing Set 3 license was activated
 It means that available user amount is 72 users. With one LCG created, 72 HSDPA users are available for LCG.
–
1 HSDPA BTS processing set 3 license was activated and two LCGs were configured.
•
•
28
Operator can commission for example 20% of all available users to LCG1 and 40% to LCG2 and this mean that remaining 40% is common
for both LCGs and can be shared freely between them.
In case when no commissioning is done, whole available amount of users is divided equally per each configured LCG.
For internal use
© Nokia Siemens Networks 2013
HSDPA license throughput distribution
Main Menu
HSDPA throughput distribution
HSDPA throughput
• Total HSDPA licensed throughput is distributed among the available HSDPA schedulers.
•
When the maximum licensed HSDPA throughput per scheduler is calculated, it is distributed between HSDPA
schedulers proportionally to "Maximum Throughput per HSDPA” commissioned values (HSDPA Throughput Step)
•
If there are only HSDPA Processing Set 1 licenses present in BTS, the division of licensed throughput will be done for
each scheduler according to the following formula:
Scheduler_licensed_throughput = Round_down { Number_of_HSDPA_Processing_Sets * (
Scheduler_HSDPA_throughput_step / Total_number_of_HSDPA_throughput_step_per_BTS) } * 7,2 Mbps
•
If there are only HSDPA Processing Set 2 and 3 licenses present in BTS, the division of licensed throughput will be
done for each scheduler according to the following formula:
Scheduler_licensed_throughput = Round_down { Number_of_HSDPA_Processing_Sets_ 2 + 4 *
Number_of_HSDPA_Processing_Sets_ 3) * ( Scheduler_HSDPA_throughput_step /
Total_number_of_HSDPA_throughput_step_per_BTS) } * 21 Mbps
29
For internal use
© Nokia Siemens Networks 2013
HSDPA license throughput distribution
Main Menu
HSDPA throughput distribution
HSDPA throughput
• If after calculations presented on previous slide, throughput for all schedulers is lower than total licensed, the
remaining throughput is distributed between schedulers with non-zero commissioned throughput. Schedulers are
prioritized in the following order:
• Scheduler with lowest value of licensed throughput divided by commissioned throughput;
• Master System Module is prioritized over Extension System Module
•
30
Scheduler with lowest ID is prioritized
For internal use
© Nokia Siemens Networks 2013
HSDPA scheduler characteristic
For internal use
Unique document identifier (ID) / Version number / Life cycle status
31
© Nokia Siemens Networks 2013
HSDPA scheduler characteristic
Main Menu
Description
• System Module rel.2 HSDPA scheduler supports up to 6 cells and provide capacity of 240 HSDPA users.
• Single HSDPA scheduler can support cells from different LCGs (LCGs using System Module rel.2 baseband
capacity)
• A-DCH/SRB resources (Rel.99 CE) are allocated at the same System Module as HSDPA scheduler.
• Single HSDPA scheduler can schedule up to 12 HSDPA users per TTI (max 4 users per cell). When 2 Tcell groups
belonging to same scheduler are used, then up to 6 users per Tcell group per TTI can be scheduled.
• Up to 2 HSDPA scheduler can be activated with single System Module rel.2
Max. number of Active
Users per HSDPA
scheduler
Max number of cells
assign to HSDPA
scheduler
Max scheduler
throughput
Max amount of
scheduled users per
TTI
240
6
252 Mbps
12
Single System Module Rel.2 HSDPA scheduler description
32
For internal use
© Nokia Siemens Networks 2013
Tcell grouping
For internal use
Unique document identifier (ID) / Version number / Life cycle status
33
© Nokia Siemens Networks 2013
Tcell grouping
Main Menu
Description
• Tcell grouping is used to group cells to the HSDPA scheduler
• Tcell groups 1 and 3 are handled by the first scheduler in System Module Rel.2 and Tcell groups 2 and 4 are
handled by the second scheduler System Module Rel.2.
• The same TCell values can be used by different cells if those are allocated to different frequency layers.
• With Dual Cell HSDPA feature both cells from one sector must have the same Tcell value. Note that with the dual cell
feature, two cells from the same sector need to be served by the same scheduler and belong to the same LCG.
• One scheduler can handle up to two Tcell groups. If there is only one Tcell group used, six cells can be supported. If
there are two Tcell groups assigned to the same scheduler, up to three cells per Tcell group can be supported
(still up to six cells are supported totally).
• The principles of grouping (maximum four TCell groups per LCG are possible) are as follows:
Group 1: Tcell values 0, 1 and 2
Group 3: Tcell values 6, 7 and 8
Group 2: Tcell values 3, 4 and 5
Group 4: Tcell value 9
34
For internal use
© Nokia Siemens Networks 2013
Tcell grouping
Main Menu
Examples 1/3
f1
f1
f2
f2
RF
modules
RF
modules
System Module
System Module
12 HSDPA cells, DC HSDPA
activated, 2 HSDPA schedulers
Scheduler 1
12 HSDPA cells, DC HSDPA not
activated*, 2 HSDPA schedulers
Scheduler 1
Scheduler 2
Scheduler 2
f1
Tcell =
0
Tcell =
1
Tcell =
2
Tcell =
3
Tcell =
4
Tcell =
5
f1
Tcell =
0
Tcell =
1
Tcell =
2
Tcell =
3
Tcell =
4
Tcell =
5
f2
Tcell =
0
Tcell =
1
Tcell =
2
Tcell =
3
Tcell =
4
Tcell =
5
f2
Tcell =
0
Tcell =
1
Tcell =
2
Tcell =
3
Tcell =
4
Tcell =
5
DC HSDPA
35
* Conditions for DC
HSDPA not met e.g.
lack of DC HSDPA
license
For internal use
© Nokia Siemens Networks 2013
Single carrier HSDPA
Tcell grouping
Main Menu
Examples 2/3
Single carrier DC HSDPA
HSDPA
f1
f2
f3
f4
f1
f2
f3
f4
RF
modules
Note: Tcell configuration is also
proper for single carrier HSDPA
(when DC HSDPA is not
activated)
System Module
System Module
12 HSDPA cells, 2 HSDPA schedulers
activated, DC HSDPA activated
Scheduler 1
Note: Tcell configuration is also
proper for single carrier HSDPA
(f3, f4 when DC HSDPA is not
activated)
RF
modules
12 HSDPA cells, 2 HSDPA schedulers
activated, DC HSDPA activated (f3,f4)
Scheduler 2
Scheduler 1
Scheduler 2
f1
Tcell =
0
Tcell =
1
Tcell =
2
f3
Tcell =
3
Tcell =
4
Tcell =
5
f1
Tcell =
0
Tcell =
1
Tcell =
2
f3
Tcell =
3
Tcell =
4
Tcell =
5
f2
Tcell =
0
Tcell =
1
Tcell =
2
f4
Tcell =
3
Tcell =
4
Tcell =
5
f2
Tcell =
6
Tcell =
7
Tcell =
8
f4
Tcell =
3
Tcell =
4
Tcell =
5
36
For internal use
© Nokia Siemens Networks 2013
Tcell grouping
Main Menu
Examples 3/3
f1
f2
f3
f2
f3
RF
modules
f2
f3
37
For internal use
© Nokia Siemens Networks 2013
Tcell =
0
Tcell =
1
Tcell =
6
Tcell =
0
Tcell =
1
Tcell =
6
Scheduler 1
System Module
12 HSDPA cells, 2 HSDPA schedulers activated,
DC HSDPA activated (f2,f3)
Scheduler 2
Scheduler 1
Tcell =
0
Tcell =
1
Tcell =
2
Tcell =
0
Tcell =
1
Tcell =
2
f1
Tcell =
3
Tcell =
4
Tcell =
5
2 Tcell groups assigned
to one scheduler -> up to
three cells per Tcell
group can be supported
(still up to six cells are
supported totally).
Network planning parameters
Access baseband capacity
Abbreviated name
accessBbCapacity
Parameter name
Access baseband capacity
Data type
%
Description
Defines the LCGs access to Baseband Capacity from 0 to 100% for HW rel.2/HW rel.3 BTS (SM and/or RF
modules) configuration. Parameter defines proportion of BB capacity available for each LCG. Flexible baseband
pooling is not possible when at least one HW rel.1 is used (SM or RF module).
Parameter group
-
Classification
LCELGW
Range and step
0 - 100
Default value
0
Access baseband capacity:
X% LCG1; Y%LCG2
Access baseband capacity:
X% LCG1; Y%LCG2
LCG 1
LCG 2
FSME
LCG 1
FSME
LCG 2
FSME
Note: To support ‘Flexible BB
pooling’ HW rel.2/HW rel.3
configuration is needed
(System Modules and RF
Modules)