Single RAN, Rel. SRAN 18 SP, Operating Documentation, Issue 01

Single RAN, Rel.
SRAN 18 SP,
Operating Documentation,
Issue 01
SBTS Dimensioning
DN09257073
Issue 06
Approval Date 2018-06-15

SBTS Dimensioning
The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective
company within Nokia Group of Companies with whom you have entered into the Agreement (as defined
below).
This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the
purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is
distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form
or means without the prior written permission of Nokia. If You have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia welcomes your comments as part of the process of
continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such
information and statements without notice. Nokia has made all reasonable efforts to ensure that the
content of this document is adequate and free of material errors and omissions, and Nokia will correct
errors that You identify in this document. Nokia's total liability for any errors in the document is strictly
limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product
will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL
OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS
DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS
FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia proprietary and confidential information, which may not be distributed or disclosed
to any third parties without the prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners.
Copyright © 2018 Nokia. All rights reserved.
f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We
would like to encourage you as our customers and users to join us in working towards a cleaner, safer
environment. Please recycle product packaging and follow the recommendations for power use and proper
disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia for any additional information.
2 © 2018 Nokia. Nokia confidential. DN09257073 Issue: 06
SBTS Dimensioning
Table of Contents
This document has 55 pages

Summary of changes..................................................................... 6

1 Overview of the SBTS dimensioning..............................................8
1.1 Dimensioning and capacity............................................................ 8
1.2 SBTS System Modules.................................................................. 8
1.3 Cell sets....................................................................................... 12
1.4 Common transport....................................................................... 13
1.5 Licenses....................................................................................... 14

2 Baseband dimensioning...............................................................15
2.1 GSM baseband dimensioning in SBTS........................................15
2.2 WCDMA baseband dimensioning in SBTS.................................. 15
2.2.1 Flexi Multiradio 10 BTS................................................................ 15
2.2.2 Fundamentals of Flexi Multiradio 10 BTS baseband dimensioning.
16
2.2.3 Nokia AirScale BTS......................................................................20
2.2.4 Fundamentals of Nokia AirScale BTS baseband dimensioning...20
2.2.5 Common Control Channels dimensioning ...................................25
2.2.6 Dedicated channels (DCH) dimensioning.................................... 30
2.2.7 HSDPA dimensioning................................................................... 31
2.2.8 HSUPA dimensioning .................................................................. 39
2.2.9 Multi RAB..................................................................................... 45
2.3 LTE baseband dimensioning in SBTS..........................................46

3 Common transport dimensioning in SBTS................................... 47
3.1 SBTS common transport dimensioning process.......................... 47
3.2 Dimensioning based on traffic profile (recommended).................47
3.3 Dimensioning based on air interface capabilities......................... 48
3.4 Transport overhead and dimensioning example.......................... 51
3.5 Estimation of C/M/S-Planes bit rate............................................. 52
3.6 Mutliplexing gain.......................................................................... 52

4 SRAN capacity licenses............................................................... 55
DN09257073 Issue: 06 © 2018 Nokia. Nokia confidential. 3
SBTS Dimensioning
List of Figures
Figure 1 Flexi 10 BTS System Module............................................................... 9
Figure 2 GSM-LTE shared System Module configuration.................................. 9
Figure 3 GSM-WCDMA shared System Module configuration with WCDMA
deployed on both FBBA/C.................................................................... 9
Figure 4 WCDMA-LTE shared System Module configuration with WCDMA and
LTE deployed on both FBBA/C.............................................................9
Figure 5 2xFSMF configuration........................................................................ 10
Figure 6 AirScale System Module components................................................ 11
Figure 7 FSMF and ASMI single and dual configurations................................ 12
Figure 8 Cell set concept ................................................................................. 13
Figure 9 FSMF structure...................................................................................16
Figure 10 Shared FSMF structure...................................................................... 16
Figure 11 Number of available subunits............................................................. 18
Figure 12 Example presenting FSMF, 1 LCG, 12 HSPA cells and one
interference cancellation unit..............................................................19
Figure 13 System Module R99 CE capacity....................................................... 20
Figure 14 AirScale System Module physical view ............................................. 20
Figure 15 WCDMA – GSM card sharing case (a)...............................................22
Figure 16 WCDMA – GSM card sharing case (b)...............................................22
Figure 17 WCDMA – LTE card sharing case...................................................... 22
Figure 18 Example of FDD-LTE and WCDMA LCG BB cards sharing (12
subunits)............................................................................................. 23
Figure 19 6 SU Digital Signal Processors (DSP) group......................................28
Figure 20 Example picture showing carrier aggregation DB/DC-HSDPA UEs
connected via primary serving cell (PSC) and secondary serving cell
(SSC)..................................................................................................34
Figure 21 System Module example of Tcell configurations (1LCG) (1/2)........... 37
Figure 22 System Module example of Tcell configurations (1LCG) (2/2)........... 37
Figure 23 Approaches to SBTS common transport dimensioning......................47
Figure 24 Approaches based on air interface capabilities.................................. 48
Figure 25 Dimensioning based on air interface capacity with carrier aggregation.
49
Figure 26 Inter-site carrier aggregation.............................................................. 50
Figure 27 Example of SBTS common transport dimensioning based on air
interface capabilities without LTE carrier aggregation........................ 51
Figure 28 Calculation of the multiplexing gain.................................................... 53
Figure 29 LTE and HSDPA cells load multiplexing gain..................................... 54
SBTS Dimensioning
List of Tables
Table 1 Number of subunits available in FSMF and FBBA/C extension cards...
16
Table 2 Number of subunits available in Flexi 10 BTS System Module.......... 17
Table 3 Number of subunits available per SBTS with one FSMF with single
LCG.................................................................................................... 19
Table 4 Number of HSDPA subunits required for the second and every next
LCG.................................................................................................... 19
Table 5 WCDMA capacity correspondence with ASMI HW configuration.......21
Table 6 Dedicated RATs and its correspondent WCDMA BB capacity for a
single ABIA......................................................................................... 23
Table 7 HSDPA scheduler allocation scenarios.............................................. 24
Table 8 Exemplary WCDMA capacity allocation SU (1x LCG scenario)......... 24
Table 9 Number of CCCH pools and RHE capacity in the FSMF HSDPA
scheduler subunits..............................................................................26
Table 10 LCG dimensioning.............................................................................. 27
Table 11 Normal HSPA LCG configurations......................................................29
Table 12 Small HSPA LCG configurations........................................................ 29
Table 13 Baseband resources required per one R99 traffic channel................ 30
Table 14 Required HSDPA subunits for HSDPA schedulers versus LCG
configurations (Flexi Multiradio 10 BTS).............................................32
Table 15 Required HSDPA subunits for HSDPA schedulers per LCG versus
LCG HSPA configuration (Flexi Multiradio 10 BTS)........................... 33
Table 16 Required HSDPA subunits for HSDPA schedulers per LCG versus
LCG HSPA configuration and number of cells (Flexi Multiradio 10
BTS)................................................................................................... 33
Table 17 CA DB/DC HSDPA users capacity (Flexi Multiradio 10 BTS).............34
Table 18 CA DC users capacity (Nokia AirScale BTS)..................................... 35
Table 19 Associated DCH and Rel.99 CE usage.............................................. 35
Table 20 Tcell values handled by HSDPA schedulers (Flexi Multiradio 10
BTS)................................................................................................... 36
Table 21 Tcell grouping (Nokia AirScale BTS).................................................. 36
Table 22 Tcell values handled by HSDPA schedulers when RAN3067: Flexible
HSDPA Carriers Allocation is enabled................................................38
Table 23 Maximal supported SBTS configuration with NBIC and PIC (FSMF).....
41
Table 24 Number of subunits reserved from the LCG capacity after NBIC
activation (FSMF)............................................................................... 42
Table 25 Number of subunits reserved from the LCG capacity after NBIC
activation (ASMI)................................................................................ 42
Table 26 Up to three HSUPA UEs with 16QAM transmission can be allocated in
a single subunit in the FSMF.............................................................. 44

Summary of changes SBTS Dimensioning
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes between issue 05 (2018-03-21, SRAN 18) and issue 06 (2018-06-15, SRAN
18 SP)
Added a note on cell capacity and baseband pooling in Fundamentals of Nokia AirScale
BTS baseband dimensioning section.
Added a note on two CCCH pools in four subunit AirScale System Module LCG in CCCH
dimensioning details section.
New configurations added:
• AirScale System Module (ASMI) components updated in SBTS System Modules
section
• FSMF and ASMI single and dual configurations in SBTS System Modules section
• AirScale System Module physical view updated Figure 14: AirScale System Module
physical view
• Nokia AirScale BTS cards in AirScale System Module baseband capacity section
• ASMI HW configuration table in AirScale System Module baseband capacity section
• LCG paramaters: smodDN, accessBbCapacity in CCCH resources allocation
section
Changes between issue 04C (2018-03-20, SRAN 17A MP1) and issue 05 (2018-03-
21, SRAN 18)
SRAN 18 supports single common unit configurations in ASMI. Updated information is in
Overview of the SBTS dimensioning and in WCDMA baseband dimensioning in SBTS.
RAN 3372 High Rate HD Voice feature impacts the WCDMA baseband dimensioning in
SBTS.
Narrow band interference cancellation (NBIC) is introduced in the HSUPA dimensioning
chapter. All WCDMA baseband dimensioning in SBTS chapter has been updated
accordingly with NBIC information.
Inter-site carrier aggregation information has been introduced in the Common transport
dimensioning in SBTS.
SRAN capacity licenses chapter has been updated.
Changes between issue 04B (2018-02-19, SRAN 17A MP0.1) and issue 04C (2018-
03-20, SRAN 17A MP1)
Dual core Nokia AirScale BTS and 2xFSMF configurations have been introduced in the
Overview of the SBTS dimensioning chapter and WCDMA baseband dimensioning in
SBTS chapter.
WCDMA baseband dimensioning in SBTS chapter has been restructured. Also it has
been added:
• Four way Rx Div information

SBTS Dimensioning Summary of changes
• Full subrack Nokia AirScale BTS support
• smodDN parameter and accessBbCapacity parameter

Overview of the SBTS dimensioning SBTS Dimensioning
1 Overview of the SBTS dimensioning
1.1 Dimensioning and capacity

An overall view of the document content and its concepts.
The SBTS Dimensioning document covers baseband (BB) dimensioning, transport
dimensioning, and capacity licenses.
Dimensioning refers to the actions and resources (HW and SW) required to achieve the
necessary capacity. The dimensioning of the network means allocating sufficient network
resources, such as frequency spectrum, time spacing and number of cips per each user,
so as to achieve the contracted user equipment traffic as both speed and data usage.
Capacity in a telecommunications network refers to the availability of the network to
process the user traffic. This term addresses strictly the user traffic, not the signalling
between the user equipment and the network. It means the resources (frequency and
time spacing) needed by the network to process the telecommunications traffic thus
acquiring the demanded parameters values as per user quota.
The information on BB dimensioning and capacity refers to two types of System
Modules: Flexi 10 BTS System Module (FSMF) and AirScale Indoor System Module
(ASMI).
Within these System Modules, three technologies are configured: GSM, WCDMA, and
LTE. GSM baseband dimensioning relies on the number of supported TRXs. WCDMA
baseband dimensioning explains how to translate the number of subunits into specific
configurations. LTE baseband dimensioning is defined by the number of cell sets.
SRAN 17A introduces the concept of cell sets, thus replacing profiles, to describe
supported configurations. These configurations are defined by BB and radio frequency
(RF) cell sets. One cell set is formed of one BB set and one or multiple RF sets.
1.2 SBTS System Modules

The System Modules supported by the SBTS are Flexi 10 BTS System Module and
AirScale System Module.
Flexi 10 BTS System Module is part of Flexi Multiradio 10 BTS and AirScale System
Module is part of Nokia AirScale BTS.
Flexi 10 BTS System Module
Flexi 10 BTS System Module is a lean SRAN site solution with System Module sharing,
fiber sharing, and RF sharing possibilities. It is a multi radio platform for GSM, WCDMA,
and LTE.

SBTS Dimensioning Overview of the SBTS dimensioning
Figure 1 Flexi 10 BTS System Module
Flexi 10 BTS System Module baseband capacity can be shared between GSM and LTE,
or GSM and WCDMA. FSMF or FBBC card baseband capacity cannot be shared
between LTE and WCDMA.
In the System Module Sharing mode, GSM is allocated at the FSMF core (not FBBA/C
card).
Figure 2 GSM-LTE shared System Module configuration
GSM LTE TRS
Additional baseband resources for WCDMA can be allocated with FBBA/C cards.
Figure 3 GSM-WCDMA shared System Module configuration with WCDMA
deployed on both FBBA/C
GSM WCDMA TRS

FBBA/C:WCDMA FBBA/C:WCDMA
Figure 4 WCDMA-LTE shared System Module configuration with WCDMA and LTE
deployed on both FBBA/C
WCDMA TRS
FBBA/C:LTE FBBA/C:WCDMA
SBTS capacity can be extended by using two system modules. The 2xFSMF obtained
configuration is a powerful and scalable SBTS solution.

Figure 5 2xFSMF configuration
g Note:
• WCDMA and GSM applications are always deployed on the first FSMF.
• LTE RAT application always utilize the second FSMF (without backhaul connection).
– Up to 3xBCS or 1xECS + 1xBCS available.
• Only two meter SRIO and OBSAI fibers (FUFAS or FSFL fibers) are supported for
connection between the FSMFs.
– Only one OBSAI and SRIO fiber can be used between the FSMFs.
– OBSAI ports used for interconnection are defined by cell sets configuration.
• RF modules with LTE cells deployed are always connected to the second FSMF.
g Note: Different LTE software allocations are possible in single BTS (for example, 2x
BCS or RCS + BCS) assuming suitable hardware capacity is available.
Reduced cell set (RCS):
• Up to 4x10MHz LTE 2x2 MIMO without CoMP
• Up to 3x10MHz LTE 2x2 MIMO with CoMP
Basic cell set (BCS):
• Up to 6x10MHz LTE 2x2 MIMO
• Up to 3x10MHz LTE 4TX/4RX1)
• Up to 3x20MHz LTE 2x2 MIMO
Extended cell set (ECS):
Up to 3x20 MHz LTE 4TX/4RX or 4x4 MIMO.
g Note: 4x4 MIMO with any cell bandwidth requires ECS.
1) 4TX/4RX = 4x2 MIMO in TM4 or/and 4RX diversity mode

g Note:
• RCS can be deployed only on FSMF shared with GSM.
• For BCS, LTE needs to be deployed on FSMF or FBBC.
• For ECS, LTE needs to be deployed on FSMF and FBBC or on two FBBC cards.
AirScale System Module

The AirScale System Module is set up indoor as well as outdoor, but a special cover is
required for outdoor capability. ASMI supports System Module sharing (SRAN)
functionality. A single BB card can be shared between two RATs. The AirScale System
Module baseband dimensioning rules are interconnected between technologies (GSM,
WCDMA, and LTE- per logical SBTS), because all technologies use ABIA cards.
Figure 6 AirScale System Module components
ABIA ABIA
ABIA ABIA
ABIA ABIA
ASIA ASIA
half subrack half subrack
AMIA subrack
(one logical SBTS)
The AirScale System Module has the following components:
• AirScale System Module subrack (AMIA)
– Fans
– Backplane for high-speed signals and power distribution

• AirScale System Module Common Plug-In-Unit (ASIA)
– Processor board for centralized control
– Up to two units in one subrack for independent base stations or high capacity
configurations
– Integrated Ethernet transport termination on subrack side
– Connectivity to transport and external System Module extension (AirScale SM
subrack or Flexi 10 BTS SM)
• AirScale System Module Capacity Plug-In-Unit (ABIA)
– Multi-RAT cell-specific baseband processing unit
– Up to six Plug-In-Unit (PIU) in subrack for flexible expansion of BTS baseband
capacity
– RF Module connectivity: 6 x OBSAI/CPRI up to 9.8 Gbps
– A single card can handle up to two RATs
Figure 7 FSMF and ASMI single and dual configurations
Flexi 10 BTS System Module AirScale System Module
Single FSMF configurations Dual FSMF configurations Single common unit Dual common unit
configurations configurations
One logical SBTS
One subrack (AMIA) has two logical SBTSs. Half subrack is seen as one logical SBTS
that includes GSM, WCDMA, and FDD-LTE. The other half subrack is used for TDD-LTE.
A full ASMI subrack support brings four RATs within one Nokia AirScale BTS.
SRAN 17A MP1 introduces dual FSMF configurations and the full ASMI subrack support
as one logical SBTS, compared to single FSMF configurations and single common unit
configurations, seen as single logical BTS until this release. AirScale System Module full
subrack means no WCDMA baseband pooling between half subracks. WCDMA does not
allow to share baseband resources between cores.
1.3 Cell sets

SRAN17A introduces the concept of cell sets to describe supported configurations.
SBTS 17A supported configurations are defined by baseband (BB) and radio frequency
(RF) cell sets. One cell set is formed of one BB set and one or multiple RF sets. During
the SBTS installation, the operator has to assure that the RF sets are connected to the
proper SM ports. The SBTS autonomously decides which baseband unit resources are
used to handle given type of carriers.
BB cell sets define the supported baseband configurations available for the customers.
BB cell sets are independent configurations for the SBTS. BB cell sets depict the
capacity of the HW used per technology and which RF ports can be used to connect the

required RF units (defined in the RF cell sets) for each RAT. SRAN and LTE cell sets can
be combined together to provide the full required SBTS configuration and also to assure
half sub-rack support.
RF cell sets define the maximum available radio capacity for one specific RAT
(GSM/WCDMA/LTE) or a combination of RATs (LTE+GSM, LTE+WCDMA,
WCDMA+GSM or LTE+WCDMA+GSM).
The RF cell set is defined by the supported RATs, the supported RF units, their hardware
family number of optical cables, and their minimum speed.
The user connects the RF unit with the SM unit, according to the selected BB, RF sets,
and defined rules when constructing the SBTS configuration. These cell sets can be
combined in various ways, resulting in a more flexible configuration than in the previous
SRAN releases. The selected RF set impacts the number of carriers that are handled for
each RAT.
SRAN cell sets for shared operation (LTE-WCDMA, LTE-GSM, GSM-WCDMA) and
dedicated RAT operation (GSM and WCDMA) are defined on sub-baseband module
level and are combined as independent building blocks.
The advantages of using the cell set concept instead of static profiles, like in the previous
releases, are as follows:
• Cell sets describe configurations that are independent from each other
• Tests and releases are performed on cell set level
• The configuration flexibility allows a higher number of configurations per SRAN
release
• Wider site configuration capabilities are available
• The user can create carriers and assigns them to the detected RF HW once the
SBTS detects the RF on specific ports during the first start up
• The user can combine LTE and SRAN cell sets to build the targeted configuration
Figure 8 Cell set concept
1.4 Common transport

SRAN introduces the concept of common transport: there is only one shared transport
entity in the SBTS.

Network load is still calculated for each RAT and the total network load is the sum of
loads from each technology (GSM, WCDMA and LTE).
Transport dimensioning is based on two approaches:
• Traffic profile (recommended)
• Air interface capabilities
1.5 Licenses
A new mechanism is introduced that uses the network-wide pool concept of Centralized
SW License Server (CLS).
There is one CLS per operator’s network. SW license keys are not physically installed at
the SBTS, but are kept in the CLS.

SBTS Dimensioning Baseband dimensioning
2 Baseband dimensioning
2.1 GSM baseband dimensioning in SBTS

For information on GSM baseband dimensioning in SBTS, see BTS EDGE
Dimensioning.
g Note: Maximum number of TRXs supported in GSM is 36.
2.2 WCDMA baseband dimensioning in SBTS

SRAN18 supports Flexi 10 BTS System Module (FSMF) and AirScale System Module
(ASMI).
This chapter covers information on the Flexi 10 BTS System Module and on the AirScale
Indoor System Module baseband (BB) dimensioning.
SBTS licensing issues are covered in the SRAN capacity licenses chapter.
2.2.1 Flexi Multiradio 10 BTS

Flexi Multiradio 10 BTS is a modular, very compact, and high capacity wide-area BTS
that can be used in various indoor and outdoor installation options (such as floor, wall,
stand, pole, mast, cabinet, 19" rack) and site applications (mini, macro, and distributed
site solution).
Flexi Multiradio 10 BTS consists of the following self-supporting BTS modules:
• Radio Module (RM). Provides the Radio Frequency (RF) functionality.
RM referred capacity:
A maximum of three RF Modules can be directly connected to the Master System
Module. The 80W/6Gb OBSAI interface – supports up to three sectors.
• System Module (SM). Provides baseband capacity for processing as well as control
and transmission functionality.
SM referred capacity:
– System Module capacity depends on the System Module type.
– The number of activated Release 99 channel elements (Rel.99 CEs), HSUPA,
HSDPA, and Common Control Channel (CCCH) processing set (PS) license
keys (LK) can be increased by license control.
g Note:
– A System Module that provides synchronization is a Master System Module.
– A capacity extension System Module is an Extension System Module.
Flexi Multiradio 10 BTS referred capacity:

Baseband dimensioning SBTS Dimensioning
Flexi Multiradio 10 BTS provides up to 18 cell capacity with two-way Rx Div in single
FSMF and nine cell capacity with four-way Rx Div. The output power options are
8/15/20/30/40/60W or 80W, depending on the RF module.
g Note: RAN3017: Additional 6 WCDMA cells activation feature license key(s) are

needed whenever more than 12 cells are configured.
g Note: WCDMA cells cannot be configured on more than 32 antenna connectors in a
single RAN site.
For supported configurations, see SBTS Supported Configurations and Creating SBTS

Configurations.
The following Flexi System Modules are available:
• Flexi 10 BTS System Module (FSMF)
• Capacity Extension Sub-module for FSMF System Module (FBBA) (optional)
• Capacity Extension Sub-module for FSMF System Module (FBBC) (optional)
2.2.2 Fundamentals of Flexi Multiradio 10 BTS baseband

dimensioning
Baseband capacity
Baseband capacity is represented by subunits (SU). One subunit in FSMF has a
capacity of 96 Rel.99 CEs.
FSMF has 5.5 subunits. In case the FSMF is shared between technologies (WCDMA
and GSM on one System Module), the number of available subunits is 3.5.
Figure 9 FSMF structure
Figure 10 Shared FSMF structure
FBBA/C has six subunits.
Table 1 Number of subunits available in FSMF and FBBA/C extension cards
FSMF FBBA/C FBBA/C Number of subunits
WCDMA - - 5.5
WCDMA WCDMA - 11.5

Table 1 Number of subunits available in FSMF and FBBA/C extension cards
(Cont.)
FSMF FBBA/C FBBA/C Number of subunits
WCDMA WCDMA WCDMA 17.5
WCDMA/GSM - - 3.5
WCDMA/GSM WCDMA - 9.5
WCDMA/GSM WCDMA WCDMA 15.5
WCDMA LTE LTE 5.5
WCDMA LTE WCDMA 11.5
WCDMA/GSM LTE LTE 3.5
WCDMA/GSM LTE WCDMA 9.5
LTE/GSM LTE WCDMA 5.5
Subunits are used for the processing of:
• Common Control Channel
• Rel.99 traffic
• HSDPA cells, users, and throughput
• HSUPA users and throughput
Flexi 10 BTS System Module available capacity

The Flexi 10 BTS System Module capacity can be extended with up to two Capacity
Extension Sub-modules (FBBA/C), which are optional. FSMF and 0-2 FBBA/C Extension
Sub-modules are one pool of common baseband resources for traffic processing, unless
local cell grouping is used. In the last case, each local cell group (LCG) is a pool of
baseband resources for traffic processing from LCG cells.
Table 2 Number of subunits available in Flexi 10 BTS System Module
Flexi 10 BTS System Module Capacity Extension Sub- Number of subunits
modules
FSMF - 5.5
FSMF FBBA 11.5
FSMF FBBA + FBBA 17.5
The System Module baseband capacity available for traffic might be further impacted by
the following:
• Additional CCCH resources
• Local cell group HSPA settings
• HSDPA subunits
• Number of activated interference cancellation units (PIC pools)
• Number of local cell groups with RAN3374 Narrowband Interference Cancellation
(NBIC) feature activated
• Static HSUPA allocation

• Static high-speed forward access channel (HS-FACH) allocation
The available baseband capacity (subunits) for traffic usage after the activation of
HSDPA, PIC, NBIC, after the allocation of static HSUPA, or additional CCCH resources
can be calculated using the formula below:
Figure 11 Number of available subunits
Number_of
available_subunits!= number_of_subunits – HSDPA_subunits – subunits_for_PIC_pool –
Subunits_for_NBIC – subunits_for_static_HSUPA!-
subunits_for_additional_CCCH-!subunits_for_HS_FACH
where:
Number_of_available_subunits number of subunits available in the
System Module
subunits_for_PIC_pool number of commissioned interference
cancellation subunits
subunits_for_NBIC number of subunits for NBIC
subunits_for_static_HSUPA number of HSUPA static commissioned
subunits
subunits_for_additional_CCCH number of subunits allocated for
additional CCCH processing (CCCH
pools)
subunits_for_HS_FACH number of subunits statically allocated
for HS-FACH users
g Note: The SBTS does not have installed physical LKs. Instead they are handled by the
Operations Support System (OSS).
Available subunits (pure traffic subunits) can be used for Rel.99 dedicated channel
(DCH) users, HSDPA users (Associated DCH (A-DCH)/signaling radio bearer(SRB)),
and HSUPA users (HSUPA scheduler).

Figure 12 Example presenting FSMF, 1 LCG, 12 HSPA cells and one interference
cancellation unit
LCG
dedicated
subunits
(5.5)
HSUPA scheduler(s)+
additionalCCCH
HSDPA
HSDPA
HSDPA scheduler(s) processingbaseband
subunits(1.125) resources
PICpool
PIC HSUPA Interferencecancelation
l
subunits(1)
CCCHprocessingresourcerequiredinadvanceto:
AdditionalCCCHsubunits(0) 1)CCCHresourcesincludedinSMrel.3capacity
2)CCCHresourcesincludedinHSDPA scheduler(s)
subunits
OptionalHSUPA staticallocationsubunits(0) CommissionedresourcesforHSUPA

(optionalstaticallocation)
HSDPA
HSDPA
LCGpuretraffic PIC
subunits(3)
Puretrafficsubunits
Table 3 Number of subunits available per SBTS with one FSMF with single LCG
HSPA settings per FSMF FSMF + FBBA FSMF + 2xFBBA
LCG
Rel.99 only 5.5 11.5 17.5
Small HSPA 4.875 10.875 16.875
Normal HSPA 4.375 10.375 16.375
Table 4 Number of HSDPA subunits required for the second and every next LCG
HSPA settings per LCG HSDPA subunits
Rel.99 only 0 SU
Small HSPA 0.625 SU
Normal HSPA 1.125 SU
g Note: 0.5 SU needs to be added to the presented figures for CCCH processing. Each
LCG requires CCCH resources.
Rel.99 CE System Module capacity

The available baseband capacity referred in Rel.99 CEs after activation of HSDPA, PIC,
after the allocation of static HSUPA or the additional CCCH resources, can be calculated
using the formula below:

Figure 13 System Module R99 CE capacity
System_Module_Rel99_CE_capacity=
=Min(#commissioned_Rel99_CEs;Rel99_CE_subunit_capacity*
*Number_of_available_subunits)
where:
#commissioned_Rel.99_CEs number of available Rel.99 CE licenses
Rel.99_CE_subunit_capacity Rel.99 CE subunit capacity
number_of_available_subunits subunits available after activation of
HSDPA, PIC, NBIC, after allocation of
static HSUPA or additional CCCH
resources
As far as Rel.99 CE capacity is considered, the FSMF subunit has 96 Rel.99 CEs.
2.2.3 Nokia AirScale BTS

Nokia AirScale BTS is an essential part of the new E2E AirScale radio access solution
that changes the way networks are built. It runs all radio technologies and supports all
network architectures. There are three key components to the base station: the RF
Module (RFM), the System Module (SM) and the common software (SW). Nokia
AirScale BTS is 60% more energy efficient than earlier generation base stations and
offers maximum re-use of existing network assets – backwards compatible with Flexi
Base Station.
Figure 14 AirScale System Module physical view
ABIA (BB Capacity PIU) AMIA (Subrack)
3U
ASIA (Common PIU)

Half subrack Half subrack
Subrack (AMIA)
Capacity PIU) (Capacity extension) Capacity PIU) (Capacity extension) Plug-in unit codes AXYZ:
- A: AirScale platform products
Capacity PIU) (Capacity extension) Capacity PIU) (Capacity extension) - X: unit type (B=capacity, S=core or common
functions, M=subrack)
Capacity PIU) (Capacity extension) Capacity PIU) (Capacity extension) - Y: I for indoor
- Z: describes version, end-user visible change
Capacity PIU1) (transport and control) Capacity PIU1) (transport and control) in functionality, new letter in alphabetical order
2.2.4 Fundamentals of Nokia AirScale BTS baseband

dimensioning
AirScale System Module baseband capacity
A single Nokia AirScale BTS supports up to 24 cells with two-way Rx Div and 12 with
four-way Rx Div.

The available ASMI WCDMA baseband resources can be split into independent
baseband pools, called local cell groups (LCG).
The LCG is a pool of baseband resources dedicated for traffic and CCCH processing
from the respective cells. Access Baseband Capacity is the parameter used to
define LCG baseband capacity. System Module available baseband capacity can be split
into a number of LCGs.
Each LCG supports up to 12 two-way Rx Div cells and six four-way Rx Div. Up to four
LCGs can be created during SBTS commissioning. Another LCG is created when the
number of cells is higher than 12, or more HSPA schedulers are needed (each LCG has
its own HSUPA and HSDPA schedulers). More than one LCG is used in the Multi
Operator RAN (MORAN) case.
In SRAN 18 SP release, Nokia AirScale BTS can use one ASIA card and up to three
ABIA cards. With the introduction of the SR001621: SRAN cell sets allocation on full
AirScale module feature in the SRAN 17A maintenance package, Nokia AirScale BTS
can support two ASIA cards and up to six ABIA cards as single SBTS. WCDMA does not
support baseband pooling between the half subracks since the baseband resources are
not shared between cores.
The WCDMA baseband capacity is represented by subunits. Each ABIA card provides a
capacity of eight subunits.
Table 5 WCDMA capacity correspondence with ASMI HW configuration
HW configuration WCDMA capacity
1x ASIA + 1x ABIA 8 subunits
Subunits are used for the processing of:
• Common Control Channel (CCCH)
• Release 99 (R99) traffic
• HSDPA cells, users, and throughput
• HSUPA cells, users, and throughput
• Interference cancellation (parallel interference cancelation (PIC) pool allocation)
The LCG baseband capacity is configured during the SBTS commissioning. The smallest
LCG size is of four subunits (half ABIA card), while the maximum size is 24 subunits
(three ABIA cards), located in the same half subrack. The LCG baseband capacity is
configurable with two subunits per step.
AirScale System Module sharing

The AirScale System Module supports System Module sharing (SRAN) functionality. A
single BB card can be shared between two RATs.
WCDMA – GSM card sharing case (a):

• Six subunits for WCDMA
• Up to 24 TRXs with ¼ ABIA for GSM
Figure 15 WCDMA – GSM card sharing case (a)
WCDMA – GSM card sharing case (b):
• Four subunits for WCDMA
• Up to 36 TRXs with ½ ABIA for GSM
Figure 16 WCDMA – GSM card sharing case (b)
WCDMA – LTE card sharing case:
• Four subunits for WCDMA
• Remaining half ABIA for LTE allocation
Figure 17 WCDMA – LTE card sharing case
g Note: WCDMA LCG can also have resources in other BB cards.

Figure 18 Example of FDD-LTE and WCDMA LCG BB cards sharing (12 subunits)
Table 6 Dedicated RATs and its correspondent WCDMA BB capacity for a single
ABIA
Concurrent RAT WCDMA available capacity
LTE (half ABIA) 4 subunits
GSM (up to 24 TRXs) 6 subunits
GSM (up to 36 TRXs) 4 subunits
g Note: The WCDMA can also utilize BB resources from another ABIA card(s).
Each LCG has statically allocated baseband resources, while the remaining part is used
for dynamic traffic allocation (Rel.99, HSUPA users, and HSUPA throughput).
The LCG baseband capacity available for traffic can be further impacted by the following:
• Additional CCCH resources
• HSDPA scheduler resources
• The number of activated interference cancellation units (PIC pools)
• Static HSUPA allocation
• Static HS-FACH uplink allocation
The static baseband allocation is done during the System Module start up. The
remaining subunits after the static BB allocation (pure traffic subunits) can be used for
R99 DCH users, HSDPA users (A-DCH)/(SRB), and HSUPA users and throughput.
There are two HSDPA scheduler allocation scenarios which depend on the LCG
baseband capacity variant:
• LCG with baseband capacity of four subunits
• LCG with baseband capacity of more than four subunits (for instance, six subunits, or
eight subunits, or ten subunits, and so on)
The LCG with four subunits baseband capacity requires 1,125 subunits for the HSDPA
scheduler, thus activating one HSDPA scheduler.

The LCG that has more than four subunits baseband capacity requires 1,625 subunits
for the HSDPA scheduler, allowing the activation of up to three HSDPA schedulers.
Baseband resources allocated for the HSDPA schedulers can also be used for the
CCCH processing. This means that for the basic cell configurations, there is no need to
allocate any additional baseband resources for the CCCH processing.
Table 7 HSDPA scheduler allocation scenarios
LCG baseband Maximum HSDPA Number of CCCH pool
capacity number of cells scheduler HSDPA available with
per LCG baseband schedulers HSDPA
resources baseband
resources
4 subunits Up to 12 cells (up 1,125 subunits 1 2 CCCH pools
to 6 HSPA cells)
More than 4 Up to 12 cells 1,625 subunits 1 or 2 or 3 3 CCCH pools
subunits (R99 or HSPA
cells)
The table below presents exemplary WCDMA AirScale System Module capacity
allocation and the maximum number of HSPA/R99 users determined by the available BB
capacity and single LCG HSPA users capacity.
Table 8 Exemplary WCDMA capacity allocation SU (1x LCG scenario)
WCDMA Baseband Max amount of Max amount of
available capacity for HSUPA users (F- HSUPA users
capacity pure traffic use DPCH) (non-F-DPCH) Max amount of
Rel.99 CE
4 su (0,5xABIA) 2,875 su 220 154 276

6 su (0,75xABIA) 4,375 su 340 238 420
8 su (1xABIA) 6,375 su 500 350 612
10 su 8,375 su 620 462 804
(1,25xABIA)
12 su (1,5xABIA) 10,375 su 620 574 996
14 su 12,375 su 620 620 1188
(1,75xABIA)
16 su (2xABIA) 14,375 su 620 620 1380
18 su 16,375 620 620 1572
(2,25xABIA)
20 su (2,5xABIA) 18,375 620 620 1764
22 su 20,375 620 620 1956
(2,75xABIA)
24 su (3xABIA) 22,375 620 620 2148
g Note: Regarding the LCG baseband capacity, the table above presents one LCG case
allowing a maximum reach of 620 HSPA users. To achieve more than 620 HSPA users
per SBTS, another LCG has to be created.

2.2.5 Common Control Channels dimensioning

General information
The following downlink (DL) Common Control Channels are supported per cell in the
SBTS:
• 1 x Primary – Synchronization Channel (P-SCH)
• 1 x Secondary – Synchronization Channel (S-SCH)
• 1 x Primary – Common Control Physical Channel (P-CCPCH)
• 1 x Primary – Common Pilot Channel (P-CPICH)
• 1 x Paging Indicator Channel (PICH)
• 1 x Acquisition Indicator Channel (AICH)
• 3 x Secondary Common Control Physical Channel (S-SCCPCH)
In the uplink (UL), resources for processing of the RACH (Random Access Channel)
preamble signatures are required per cell. RACH preamble signatures are used for both
RACH users and HS CELL_FACH users.
The extended cell

The basic principles for extended cells in the SBTS are as follows:
• Cells with ranges higher than 20 km are called extended cells
• CCCH pool and CCCH PS LK dimensioning rules are the same as non-extended cell
range
• One or several cells in the SBTS (supported configurations) can be configured as
extended cells
• An extended cell is tested up to 150 km
CCCH dimensioning details

The CCCH baseband resources for signature processing of RACH preambles, for RACH
and HS CELL_FACH users, are called CCCH pools.
One CCCH pool has a capacity of 480 RACH Handler Elements (RHE).
A certain number of CCCH pools is required, depending on:
• Cell range
• #Signatures for RACH preambles
• Rx Diversity
• Number of cells in the local cell group
CCCH resources in FSMF

One CCCH pool (480 RHE) is included in a FSMF HW capacity.
The FSMF HSDPA scheduler baseband resources (HSDPA subunits) include CCCH
pools for additional CCCH processing.

Table 9 Number of CCCH pools and RHE capacity in the FSMF HSDPA scheduler
subunits
LCG HSPA #HSDPA #HSUPA HSDPA #CCCH pools #RHE in
configuration schedulers schedulers subunits in HSDPA HSDPA
subunits subunit(s)
Rel.99 only 0 0 0 0 0
Small HSPA 1 1 0.625 1 480
Normal HSPA 2 1 1.125 2 960
If additional HSDPA subunits are allocated, those contain CCCH resources that can be
used for CCCH processing.
Whenever it is required from the CCCH point of view, CCCH pools from HSDPA subunits
are used for CCCH processing.
Whenever it is required from the CCCH point of view, and CCCH pools from HSDPA
subunits are not sufficient, additional CCCH pools on top of HSDPA subunits are
allocated.
One commissioned CCCH processing set enables one CCCH pool included in the
HSDPA subunits. Each commissioned CCCH processing set requires one processing set
license key (CCCH PS LK), which is handled by the OSS.
One additional CCCH pool consumes 0.5 SU.
Every LCG that has NBIC activated, gets one additional CCCH pool. This additional
CCCH pool from NBIC resources is enabled for use with one CCCH PS LK.
A four subunit AirScale System Module LCG gets two additional CCCH pools but one
subunit is needed for the NBIC allocation. In such case, these additional CCCH pools
from NBIC resources require two CCCH PS LKs to be used for CCCH processing.
CCCH resources in ASMI
Every System Module in the SBTS configuration has one CCCH PS (480RHE) included
in the HW price, which does not require any license. One CCCH processing set is
available by default per each AirScale System Module and does not require any
configuration.
Each LCG in the AirScale System Module contains CCCH baseband processing
resources (named CCCH pools) included in the HSDPA scheduler baseband capacity.
The ASMI LCG has a number of two or three CCCH pools included in the HSDPA
subunits.
Additional CCCH pools (on top of the CCCH pools from the HSDPA scheduler baseband
resources) are allocated when needed.
Additional CCCH pools or CCCH pools from the HSDPA scheduler baseband resources
are enabled, when they are licensed with CCCH PS LK.
A single pool of CCCH provides a capacity of 48 RACH resources, which are common
for all assigned cells. One RACH resource is used to process one RACH message
during 10ms packet random access channel (PRACH) radio frame.
In case of 20ms RACH transmission time interval (TTI), one RACH message consumes
two RACH resources.

Table 10 LCG dimensioning
LCG baseband Maximum number of CCCH pool available RHE
capacity cells per LCG with HSDPA
baseband resources
4 subunits Up to 12 cells 2 CCCH pools 960
(maximum 6 HSPA
cells)
More than 4 subunits Up to 12 cells (R99 or 3 CCCH pools 1440
HSPA cells)
Common features for Flexi Multiradio 10 BTS and Nokia AirScale BTS
The CCCH resources are LCG specific. Each LCG must have CCCH resources (CCCH
pool(s)) for cells that are mapped to a particular LCG.
The RHE is a processing resource of a CCCH pool that is used for processing the RACH
channel of a cell within a LCG.
The required RHE per cell in a LCG is calculated with the following formula:
#RHE_per_cell = CellRange*#Signatures*RxDiv
where:
• #RHE_per_cell – number of required RACH Handler Elements per single cell (max
480)
• CellRange – cell range, referred to in kilometers, rounded up to whole integer
divisible by five
• #Signatures – number of signatures for RACH preambles
• RxDiv – Rx Diversity. Takes a value of two for two-way Rx Div or four in case of four-
way Rx Div
One CCCH pool supports the following number of cells (four RACH signatures per cell
are assumed):
• 3 cells/20 km 2-Way RX Div
(#RHE_per_cell=20*4*2=160 RHE; 3 cells require 3*160 RHE=480 RHE)
(#RHE_per_cell=10*4*2=80 RHE; 6 cells require 6*80 RHE=480 RHE)
(#RHE_per_cell=10*4*4=160 RHE; 3 cells require 3*160 RHE=480 RHE
Other numbers of cells per CCCH pool are also supported.
The following is a list of basic configurations that are served with one CCCH pool
included in the System Modules HW capacity, and do not require any additional
resources for CCCH processing:
• 1xSystem Module: 3 cells/20 km 2-Way Rx Div
• 1xSystem Module: 6 cells/10 km 2-Way Rx Div
Whenever the CCCH resources included in the HSDPA subunits are not enough,
additional CCCH resources are allocated with granularity of 0,5 subunit (one CCCH
pool). In Nokia AirScale BTS, baseband subunits are grouped by two. Only one CCCH

pool can be allocated per group (two subunits). Each PIC activation excludes additional
CCCH processing resources allocated in the grouped subunits. Only one PIC pool can
be associated per baseband subunits group.
Figure 19 6 SU Digital Signal Processors (DSP) group
To activate the CCCH pools, the proper amount of CCCH processing sets need to be
configured. One CCCH processing set is available by default per each AirScale System
Module and does not require any configurations.
CCCH resources allocation

The CCCH resources are local cell group specific.
Each LCG must have CCCH resources (CCCH pools) for the cells that are mapped to a
particular LCG.
The CCCH resources included in the SBTS HW are not connected with a particular
System Module.
In case of a SBTS with one System Module and multiple LCGs, the CCCH resources
included in the HW capacity are assigned to LCG#1. LCG#2, LCG#3, and LCG#4
require at least one CCCH pool.
In case of a dual core AirScale, smodDN parameter identifies the half subrack where the
HW resources are allocated for the local cell group.
LCG baseband capacity is defined with Access Baseband Capacity parameter.
The sum of accessBbCapacity which points to the same smodDN must be "100".
Example: BB capacity distribution in LCGs

Primary core:
• LCG1 - accessBbCapacity = 40%

• Sum = 100%
Secondary core:
• Sum = 100%
Required CCCH resources for basic configurations

The number of signatures for RACH preambles is defined with the parameter
RACHPreambleSignatures (WCEL). It specifies the number of signatures used for
RACH users and HS CELL_FACH users (RAN1913: High Speed Cell_FACH). The
FSMF summarizes the required number of subunits and CCCH license keys (FSMF) for
some of the cell configurations.
Normal HSPA local cell group
Table 11 Normal HSPA LCG configurations
CellRange 5 10 15 20 5 10 15 20
Cells Signatures \ 2 2 2 2 4 4 4 4
RX Div
3 4 -\- -\- -\- -\- -\- -\- 1\- 2\-
6 4 -\- -\- 1\- 1\- -\- 1\- 2\- 5\1
9 4 -\- 1\- 2\- 2\- 1\- 2\- 4\1 8\2.5
12 4 -\- 1\- 2\- 3\0.5 1\- 3\0.5 5\1.5 11\4
3 8 -\- -\- 1\- 2\- -\- 2\- 2\0 N/A1)
6 8 -\- 1\- 2\- 5\1 1\- 5\1 5\1.5 N/A1)
9 8 1\- 2\- 4\1 8\2.5 2\- 8\2.5 8\3 N/A1)
12 8 1\- 3\0.5 5\1.5 11\4 3\0.5 11\4 11\4.5 N/A1)
The table above presents the number of CCCH processing set LKs divided to the
number of additional subunits required for CCCH processing, versus number of cells, cell
range (km), Rx Div mode and number of RACH preamble signatures in the FSMF normal
HSPA LCG.
Small HSPA Local Cell Group
Table 12 Small HSPA LCG configurations
CellRange 5 10 15 20 5 10 15 20
Cells Signatures \ 2 2 2 2 4 4 4 4
RX Div
3 4 -\- -\- -\- -\- -\- -\- 1\- 2\-
6 4 -\- -\- 1\- 1\- -\- 1\- 2\0.5 5\1.5
3 8 -\- -\- 1\- 2\- -\- 2\- 2\0.5 N/A1)
6 8 -\- 1\- 2\0.5 5\1.5 1\- 5\1.5 5\2 N/A1)

The table above presents the number of CCCH processing set LKs divided to the
number of additional subunits required for CCCH processing, versus number of cells, cell
range (km), Rx Div mode and number of RACH preamble signatures in FSMF small
HSPA LCG.
g Note: One CCCH PS LK per FSMF System Module is included in HW price, which is
shown in the tables above. One CCCH PS LK and 0.5 SU need to be added to the
presented figures in case of LCG#2, LCG#3, and LCG#4 in FSMF. In case of LCG#1,
the number of CCCH PS LKs and number of additional required subunits is directly
applicable.
2.2.6 Dedicated channels (DCH) dimensioning

For baseband dimensioning purposes, a certain number of R99 channel element (CE)
per active DCH user is required. Baseband resources are required per DCH active user
in “no handover” state, and per DCH user in “soft handover” state. Additional baseband
resources are not required for users in softer handover state or in compressed mode.
The number of R99 CE depends on the radio access bearer (RAB) data rate and
minimum spreading factor (SF). The table below presents the required number of R99
CE per each active connection for basic set of RABs.
The RAN3372 High Rate HD Voice feature (WCDMA18) extends the support of AMR
Codecs with WB-AMR Codec 23.85 kbps. WB-AMR provides significantly superior voice
quality. As the resource required to support higher rate codecs is higher as well, these
higher rates are used when there are enough resources. The table below also provides
details on the required resources for WB-AMR.
Table 13 Baseband resources required per one R99 traffic channel
RAB Traffic CS /PS Max Min SF Min SF Required Required

class Rates for R99 CE per R99 CE per
UL DL
each connection connection
RAB,
UL DL
kbps
AMR Conversat CS 1.2 64 128 1 1

Speech ional
Speech ional
Speech ional
Speech ional
Speech ional
Speech ional
Speech ional
Speech ional

Table 13 Baseband resources required per one R99 traffic channel (Cont.)
RAB Traffic CS /PS Max Min SF Min SF Required Required

class Rates for R99 CE per R99 CE per
UL DL
each connection connection
RAB,
UL DL
kbps
Packet Interactive PS 16 64 128 1 1

/Backgrou
nd
/Backgrou
nd
/Backgrou
nd
/Backgrou
nd
/Backgrou
nd
/Backgrou
nd
UDI Conversat CS 64 16 32 4 4
ional
Streamin Streaming CS 57.6 16 32 4 4
g
Streamin Streaming CS 14.4 64 128 1 1
g
Asymmetric UL/DL R99 CE allocation

Asymmetric UL/DL allocation means that the UL and DL directions have different bit rate
requirements. The rule for allocating resources for asymmetric bit rates is based on a
higher data rate requirement, but R99 CE reservations are done separately for UL/DL.
For example, if the UL bearer is 64 kbps and the DL bearer is 384 kbps, the R99 CE
reservation is four R99 CE in UL and eight R99 CE in DL.
UL and DL resources have to be allocated inside one subunit, but there is no direct
connection between UL and DL resource allocation. In other words, UL and DL
resources do not need to be allocated symmetrically across subunit UL and DL capacity.
2.2.7 HSDPA dimensioning

HSDPA scheduler
The HSDPA scheduler provides high throughput capability. From the baseband
perspective, achievable HSDPA throughput further depends on the activated features
(for example RAN1906: Dual-Cell HSDPA 42Mbps, RAN2179: Dual Band HSDPA
42Mbps) and HSDPA throughput commissioning.

The HSDPA scheduler provides a high number of user capability. The achievable
number of active HSDPA users, further depends on the activated features (RAN2124:
HSPA 128 Users Per Cell, RAN2869: HSPA Subscriber Increase).
The HSDPA scheduler does not consume any R99 CE LKs.
The HSDPA scheduler supports 64 quadrature amplitude modulation (QAM), dual cell
(DC)-HSDPA, and dual band (DB)-HSDPA features.
The number of supported users per cell, depending on the enabled capacity license, is
as follows:
• Up to 208 users per cell (RAN2869: HSPA Subscriber Increase)
• Up to 180 users (RAN3179: HSDPA HS-FACH Enhanced Queuing)
• Up to 128 users per cell (RAN2124: HSPA 128 Users per Cell)
• Up to 72 users per cell (RAN1686: HSPA 72 Users per Cell)
HSDPA, DC/DB-HSDPA, RAN3067: Flexible HSDPA Carriers Allocation: Carrier

Aggregation (CA) DC/DB-HSDPA and HS CELL_FACH DL users are counted to above
“per cell” limits.
The single HSDPA scheduler supports up to six cells.
• The HSDPA scheduler is LCG specific. It supports cells only from its own LCG.
• Up to three schedulers per LCG are supported when LCG has more than four
subunits baseband capacity. An LCG that has only four subunits supports one
HSDPA scheduler and therefore up to six HSPA cells.
• Cell or Enhanced Virtual Antenna Mapping (E-)VAM (RAN2482: Enhanced Virtual
Antenna Mapping) cells require more HSDPA subunits compared to non-(E-)VAM
cell.
• VAM cell and E-VAM cell requires the same amount of baseband resources from the
HSDPA scheduler point of view.
• Non-(E-)VAM and (E-)VAM cell requires the same amount of baseband resources
from the HSDPA scheduler point of view.
The scheduler contains CCCH resources (CCCH pools) that may be used for CCCH
processing when those are enabled with CCCH PS LK.
Table 14 Required HSDPA subunits for HSDPA schedulers versus LCG
configurations (Flexi Multiradio 10 BTS)
LCG HSPA Number of HSDPA Maximum number of HSDPA subunits
configuration schedulers supported HSDPA
cells
Rel99 Only 0 0 0
Small HSPA 1 6 0.625
Normal HSPA 2 12 1.125
The table below presents the required baseband resources for HSDPA schedulers per
LCG HSPA configurations. Assumptions: non-(E-)VAM cells, 10km cell range, two way
Rx Div and RACHPreambleSignatures = 4.

Table 15 Required HSDPA subunits for HSDPA schedulers per LCG versus LCG
HSPA configuration (Flexi Multiradio 10 BTS)
LCG HSPA configuration 1st LCG: HSDPA 2nd and next LCG: HSDPA
subunits/additional CCCH subunits1) / additional CCCH
pools pools2)
Small 0,625/1 0,625/1
Normal 1,125/2 1,125/2
1) Additional 0.5 SU (one CCCH pool/480RHE) for CCCH processing needs to be added
to the presented figures in the second and following LCGs.
2) If needed, CCCH pools can be used when CCCH PS LKs are available.
The table below presents the required baseband resources for HSDPA schedulers per
LCG for typical number of cells and for available LCG HSPA configurations.
Assumptions: (E-)VAM cells, 10km cell range, two way Rx Div and
RACHPreambleSignatures = 4.
Table 16 Required HSDPA subunits for HSDPA schedulers per LCG versus LCG
HSPA configuration and number of cells (Flexi Multiradio 10 BTS)
LCG HSPA Maximum number of 1stLCG: HSDPA 2nd and next LCG:
configuration supported HSPA subunits/additional HSDPA subunits1) /
cells per LCG CCCH pools additional CCCH
pools2)
Small Up to 4 0,625/1 0,625/1
Small 5-6 1,125/2 1,125/2
Normal Up to 6 1,125/2 1,125/2
Normal 7 – 8 1,625/3 1,625/3
Normal 9 – 10 2,125/4 2,125/4
Normal 11 - 12 2,625/5 2,625/5
1) Additional 0.5 SU for CCCH (one CCCH pool/480RHE) processing needs to be added
to the presented figures in the second and following LCGs.
2) If needed, CCCH pools can be used when CCCH PS LKs are available.
g Note: The FSMF supports up to 12 cells.
HSDPA users
One HSDPA scheduler has 240 scheduling units. The resources are used by:
• One HSDPA user or one DB/DC-HSDPA user consumes 1.0 scheduling unit from the
scheduler
• One HSDPA user in High Speed CELL_FACH state consumes 1.0 scheduling unit
from the scheduler
• RAN3067: Flexible HSDPA Carriers Allocation: One CA DB/DC-HSDPA user
consumes:

– 1.0 scheduling unit from the scheduler handling primary carrier of that user
– 0.5 scheduling unit from the scheduler handling secondary carrier of that user
Which in total gives:
– 1.5 scheduling units per one user, in total per SBTS with two HSDPA schedulers
(assuming CA DB/DC-HSDPA user is receiving data from two HSDPA schedulers
from two different LCGs)
Figure 20 Example picture showing carrier aggregation DB/DC-HSDPA UEs
connected via primary serving cell (PSC) and secondary serving cell (SSC)
The maximum number of CA DB/DC-HSDPA users per SBTS is calculated with the
following formula:
Max_#CA_HSDPA_users_BTS= 1/1.5 x 240 x#schedulers
where:
• Max_#CA_HSDPA_users_BTS- maximum number of CA DB/DC-HSDPA users per
SBTS
• #schedulers- number of HSDPA schedulers (CA requires at least two schedulers
in the SBTS)
Table 17 CA DB/DC HSDPA users capacity (Flexi Multiradio 10 BTS)
Number of HSDPA schedulers per SBTS Maximum number of CA DB/DC-HSDPA
users per SBTS
1 N/A
2 320
3 480
4 640
Example
100 HSDPA active users and 50 DC users consume Round_up (100 * 1 + 50 * 1.25) =
Round_up (100 + 62.5) = 163 scheduling units.
Therefore, additionally 240 - 163 = 77 scheduling units are unused allowing for allocation
of additional 77 HSDPA users or Round_down (77 / 1.25) = 61 DC users.

Table 18 CA DC users capacity (Nokia AirScale BTS)
Number of HSDPA schedulers in a LCG Number of CA DC users per LCG
1 160
2 320
3 480
g Note: This is the LCG level capacity considering all users handled by schedulers are
CA DC users. For mixed profiles (SC/DC and CA DC/DB users combined), the number
of users that can be supported is equal to:
[(# primary carriers for CA DC/DB) + (0.5 * # 2nd carriers
for CA DC/DB)] <= (240 * number of HSDPA schedulers in LCG)
unit of load, where one unit is the load required to handle one SC user in a core.
HS CELL_FACH users
One HSDPA user in High Speed CELL_FACH state consumes one scheduling unit.
In addition, one scheduling unit is reserved per HS_FACH (RAN1637: HS Cell_FACH DL
required) enabled cell. Each HS_FACH enabled cell consumes one scheduling unit.
Thus, an HSDPA scheduler with six cells, where each cell is HS_FACH enabled has 240
– 6 = 234 scheduling units.
Multi RAB users

One HSDPA scheduler supports 240 radio bearers. For example, in case of one Multi
RAB UE with ongoing HSDPA data download, and simultaneous HSDPA web browsing,
one scheduler can support 238 single RAB users in addition to one Multi RAB user with
two HSDPA RABs.
HSDPA Rel.99 CE consumption for A-DCH and DL SRB

An HSDPA active user consumes R99 CEs for DL SRB processing and DCH return
channel processing (A-DCH) for UL.
SRB and A-DCH Rel.99 CEs for traffic from the respective cells are allocated on the
same System Module where the HSDPA scheduler processes the respective cells.
In case of the HSDPA user with HSUPA UL return channel, R99 CEs are not consumed
at all.
The A-DCH consumption depends on the DCH data rate.
Associated UL/DL DCH

The Associated UL/DL DCH of the HSDPA user employs the capacity in the same way
as a normal DCH.
Table 19 Associated DCH and Rel.99 CE usage
User data R99 CE required in UL / Min R99 CE required in DL / Min
SF SF
PS 16 kbps 1/SF64* 1/SF128**
PS 64 kbps 4/SF16 1/SF128**

Table 19 Associated DCH and Rel.99 CE usage (Cont.)
User data R99 CE required in UL / Min R99 CE required in DL / Min
SF SF
PS 128 kbps 4/SF8 1/SF128**
PS 384 kbps 8/SF4 1/SF128**
g Note: * If SF is 32, two Rel.99 CEs are required in UL.
** One Rel.99 CE for DL signaling (SRB) is required per HSDPA user.
Tcell grouping
From the HSDPA point of view, the RNC parameter Tcell (frame timing offset of a cell) is
used to indicate which cell is processed by which scheduler. Tcell groups are handled by
the schedulers in the following way:
Table 20 Tcell values handled by HSDPA schedulers (Flexi Multiradio 10 BTS)

Scheduler 1 Scheduler 2
Tcell values from group 1 0, 1, 2 N/A
Tcell values from group 2 N/A 3, 4, 5
Tcell values from group 3 6, 7, 8 N/A
Tcell values from group 4 N/A 9
Table 21 Tcell grouping (Nokia AirScale BTS)
LCG with 4 subunits baseband Scheduler #1 Tcell group 1 and 3 (values:
capacity 0,1,2 and 6,7,8)
LCG with more than 4 subunits Scheduler #1 Tcell group 1 (value 0,1,2)
baseband capacity
Scheduler #2 Tcell group 2 and 4 (values:
3,4,5 and 9)
Scheduler #3 Tcell group 3 (values: 6,7,8)
With one scheduler and one Tcell group, up to six cells per Tcell group are supported.
With one scheduler and two Tcell groups, up to three cells per Tcell group are supported
(up to six cells are still supported in total).
The same Tcell values can be used by different cells if those are allocated to different
frequency layers.
DB/DC-HSDPA Tcell settings

The DB as well as DC HSDPA features require both cells from one sector to have the
same Tcell value. With the DB or DC feature, two cells from the same sector need to be
served by one System Module and one scheduler, and belong to the same LCG. When
both cells from the DC-HSDPA sector are in one band, those need to be from adjacent
frequencies. The DB-HSDPA enables DC functionality with two cells from different
frequency bands.
The M5000 counters indicating scheduled HSDPA users are Tcell group specific. Tcell
grouping may affect counter behavior.

Figure 21 System Module example of Tcell configurations (1LCG) (1/2)
Ff1 Ff1
Ff2 Ff2
RFmodules RFmodules
SystemModule SystemModule
12HSDPA cells,DCHSDPA activated, 12HSDPA cells,DCHSDPA not activated,

2HSDPA schedulers 2HSDPA schedulers
Scheduler1 Scheduler2 Scheduler1 Scheduler2
Ff1 Tcell=0 Tcell=1 Tcell=2 Tcell=3 Tcell=4 Tcell=5 Ff1 Tcell=0 Tcell=1 Tcell=2 Tcell=3 Tcell=4 Tcell=5
Ff2 Tcell=0 Tcell=1 Tcell=2 Tcell=3 Tcell=4 Tcell=5 Ff2 Tcell=0 Tcell=1 Tcell=2 Tcell=3 Tcell=4 Tcell=5
DCHSDPA SinglecarrierHSDPA
Figure 22 System Module example of Tcell configurations (1LCG) (2/2)
Ff1 DC-HSDPA Ff1

Ff2 notplanned
Ff2
Ff3 Ff3
DC-HSDPA
Ff4 Ff4
RFmodules RFmodules
SystemModule SystemModule
12HSDPA cells, 2HSDPA schedulersactivated, 12HSDPA cells, 2HSDPA schedulersactivated,

DCHSDPA activated(f1,f2,f3,f4) DCHSDPA activated(f3,f4)
Scheduler1 Scheduler1
Ff1 Tcell=0 Tcell=1 Tcell=2 Ff1 Tcell=0 Tcell=1 Tcell=2
Scheduler2 Scheduler2
CA DB/DC-HSDPA Tcell settings

The RAN3067: Flexible HSDPA Carriers Allocation feature enables DB/DC-HSDPA with
primary serving cell and secondary serving cell mapped to two separate LCGs, and thus
handled by two separate schedulers. In this case, CA DB/DC-HSDPA UE is connected
via primary serving cell and secondary serving cell mapped to one sector, but different
LCG. Both primary and secondary serving cells need to have the same Tcell value.
When RAN3067: Flexible HSDPA Carriers Allocation is enabled, one scheduler supports
only one of the two Tcell groups.

Table 22 Tcell values handled by HSDPA schedulers when RAN3067: Flexible

HSDPA Carriers Allocation is enabled
Scheduler 1 Scheduler 2
Tcell Values from Group 11 0, 1, 2 N/A
Tcell Values from Group 22 N/A 3, 4, 5
Tcell Values from Group 33 6, 7, 8 N/A
Tcell Values from Group 44 N/A 9
g Note: This table exemplifies Tcell values handled by HSDPA schedulers for Flexi
Multiradio 10 BTS.
g Note: 1Tcell Values 0, 1, 2 are allowed only if values 6, 7, 8 are not in use by Scheduler
1 in one LCG.
2Tcell Values 3, 4, 5 are allowed only if value 9 is not in use by Scheduler 2 in one LCG.
3Tcell Values 6, 7, 8 are allowed only if values 0, 1, 2 are not in use by Scheduler 1 in
one LCG.
4Tcell Value 9 is allowed only if values 3, 4, 5 are not in use by Scheduler 2 in one LCG.
Simultaneous HSDPA users in TTI

HSDPA scheduler supports a number of users per TTI, depending on the feature
activation:
• RAN3269: Optimized HSDPA Scheduler active.
Up to 24 HSDPA users per scheduler can be code multiplexed, and thus served
simultaneously.
If the cells of a scheduler are mapped to only one Tcell group, the scheduler supports
up to six cells and is able to select up to 24 users dynamically from the cells that
have users eligible for the transmission in the TTI.
If the cells are mapped to two Tcell groups within the same scheduler, the scheduler
supports up to three cells per Tcell group. It is able to select up to 12 users/Tcell
group dynamically from the cells within the Tcell group that has users eligible for the
transmission in the TTI.
• RAN3269: Optimized HSDPA Scheduler not active.
Up to 12 HSDPA users per scheduler can be code multiplexed and thus served
simultaneously.
If the cells of a scheduler are mapped to only one Tcell group, the scheduler supports
up to six cells and is able to select up to 12 users dynamically from the cells that
have users eligible for the transmission in the TTI (RAN3067: Flexible HSDPA
Carriers Allocation). The scheduler supports 18 users in the TTI, where 12 are from
the primary serving cells and the remaining six are from the secondary serving cells.
If the cells are mapped to two Tcell groups within the same scheduler, the scheduler
supports up to three cells per Tcell group and is able to select up to six users/Tcell
group dynamically from the cells within the Tcell group that has users eligible for the
transmission in the TTI.

With the RAN3269: Optimized HSDPA Scheduler feature, the scheduler supports up to

100% more users per TTI (up to 12 delta users). 12 delta users are selected from the
users with small packets (one Packet Data Unit (PDU)), without PDU assembly. For
example, PDU retransmission, high-speed shared control channel (HS-SCCH) order and
HS-FACH users that have small packets to transmit.
2.2.8 HSUPA dimensioning

HSUPA is supported only with the co-existence of HSDPA. HSUPA is activated per LCG.
In case of the SBTS with one System Module, HSUPA is activated per LCG and is
supported in multiple LCGs.
HSUPA scheduler
HSUPA scheduler is capable of supporting high throughputs and high number of active
users. The HSUPA active user is served in CELL_DCH. HSUPA active user is also a
user in RAN1913: High Speed Cell_FACH.
The HSUPA throughputs (CELL_DCH) can depend on activated features (for example,
RAN981: HSUPA 5.8 Mbps, RAN1702: Frequency Domain Equalizer, HSUPA 16QAM),
RAN1905: Dual Cell HSUPA as well as a number of available HSUPA BTS processing
set LKs and available baseband resources.
The number of the HSUPA users actively served in the SBTS may depend on available
baseband resources, as well as actively used features (RAN1201: Fractional DPCH).
One HSUPA scheduler is available with one LCG. Additional LCGs provide additional
HSUPA schedulers.
HSUPA traffic impact on available capacity
• The HSUPA traffic is processed by the HSUPA scheduler.
• The activation of the HSUPA scheduler has no impact on the available baseband
capacity.
• Active HSUPA users and a total HSUPA scheduler throughput have impact on the
available baseband capacity. In case of active HSUPA users, the HSUPA scheduler
in the System Module consumes HSUPA resource steps.
• The HSUPA Resource Step is a baseband capacity equivalent of a 0.125 subunits.
• R99 CEs are not consumed by the HSUPA active user allocations (neither by the
data channels or SRB) in the System Module.
• The impact of active HSUPA users on available baseband capacity depends on the
number of HSUPA users and HSUPA scheduler throughput, as well as if the HSUPA
user is actively using the following features:
– HSUPA 2ms TTI
– HSUPA 10ms TTI
– F-DPCH (RAN1201: Fractional DPCH)
– RAN3259: HSUPA Baseband Boost for non-FDPCH Users
The HSUPA active users and throughput impact on the available baseband capacity is
presented in the Flexi Multiradio 10 BTS and Nokia AirScale BTS HSUPA capacity
tables.
The subunit usage can change on the TTI basis. In one TTI, UE transmits with 16 QAM
modulation, while in the other TTI, lower modulation order is used. For example, 16 QAM
usage depends on the radio conditions or the amount of data in the UE buffer.

HSUPA dynamic resource reservation

The baseband capacity is reserved for the HSUPA dynamically, on need basis. If there
are active HSUPA users in the LCG, a certain number of HSUPA resource steps are
reserved. If the throughput is decreasing and/or the number of users is decreasing, the
reserved resources can get released, depending on the baseband resource situation in
the SBTS. If there is a need for baseband resources for higher priority traffic (for
example DCH traffic), the SBTS releases the resources fast.
If there is no baseband congestion situation, the HSUPA resource might not get released
fast. This is done to keep the HSUPA resources ready to use, especially for users with
bursty transmission. This improves latency, round trip time and end user experience as
well as instantaneous UE throughput. Therefore, a subunits utilization indicators may
appear high, but this does not necessarily indicate that the SBTS baseband resources
have reached maximum capacity. The dynamic allocation of baseband resources keeps
the HSUPA subunit utilization on a high level, although more users can be served
additionally. By allocating extra (not used) subunits for the users, the scheduling changes
are much faster (in the scale of scheduling periods), as there is no immediate need for
HW allocation changes and the new serving grants can be provided to the UEs
immediately.
For information about capacity usage monitoring, see the Managing WCDMA RAN
Capacity document.
If there are no active HSUPA users in the LCG, there is no dynamic baseband resource
reservation.
If the active HSUPA users and/or HSUPA scheduler throughput is increasing, the
resource steps are also reserved (allocated) accordingly. To allocate the next HSUPA
resource step, an additional free capacity of 12 R99 CEs is needed.
These 12 R99 CEs can have any licensed R99 CEs in any System Module. The required
six Rel.99 CE free on top of the HSUPA resource step is to avoid a “ping-pong” effect in
reserving and freeing HSUPA resource steps. This action is needed so that the HSUPA
resource step is not requested back immediately after its allocation.
When the free channel capacity drops below eight, the Resource Manager starts to
release resources used by HSUPA.
HSUPA required resource dimensioning

To calculate the required number of subunits for mixed user type cases, (F-DPCH/no-
FDPCH/2ms TTI/10msTTI users, 16QAM, DC-HSUPA), the following rule is applied. In
some cases, the rule presented below leads to overestimation of the baseband
resources. See Flexi Multiradio 10 BTS and Nokia AirScale BTS HSUPA capacity tables.
HSUPA_Subunits=F-DPCH_2msTTI_subunits+no-
FDPCH_10msTTI_subunits +
16QAM_2msTTI_subunits+HS_Cell_FACH_UL_(RAN1913)_users
where:
• F-DPCH_2msTTI_subunits – subunits required for the HSUPA F-DPCH 2ms TTI
users, calculated from the HSUPA dimensioning tables (See Flexi Multiradio 10 BTS
and Nokia AirScale BTS HSUPA capacity tables)
• F-DPCH_10msTTI_subunits – subunits required for the HSUPA F-DPCH 10ms TTI
users, calculated from the HSUPA dimensioning tables (See Flexi Multiradio 10 BTS
and Nokia AirScale BTS HSUPA capacity tables)

• No-F-DPCH_2msTTI_subunits – subunits required for the HSUPA no-F-DPCH 2ms
TTI users, calculated from the HSUPA dimensioning tables (See Flexi Multiradio 10
BTS and Nokia AirScale BTS HSUPA capacity tables)
• No-F-DPCH_10msTTI_subunits – subunits required for the HSUPA no-F-DPCH
10ms TTI users, calculated from the HSUPA dimensioning tables (See Flexi
Multiradio 10 BTS and Nokia AirScale BTS HSUPA capacity tables)
• 16QAM_2msTTI_subunits – subunits required for the UEs simultaneously
transmitting with 16QAM modulation
• HS_Cell_FACH_UL_(RAN1913)_users – subunits required for theRAN1913: High
Speed Cell_FACH (HS Cell_FACH UL)
Narrowband Interference Cancellation

The RAN3374 Narrowband Interference Cancellation feature impacts WDCMA BB
dimensioning. Narrowband interference within the SBTS receiving band is detected and
filtered out automatically and dynamically. Externally, narrowband interference within the
uplink receiving band at SBTS level can destroy the cell’s performance altogether. With
the NBIC feature, the high cost of finding and removing the external source can be
avoided, as the cell’s performance remains the same in spite of the interference spikes.
More than three times larger cell coverage can be maintained for the site, proportional
with the magnitude of narrowband interference. NBIC is supported with FSMF and ASMI.
The RAN3374 Narrowband Interference Cancellation feature is activated on LCG level
with nbicEnabled parameter when:
• LCG has up to six cells two way Rx Div or up to three cells four way Rx Div
• LCG hspaSettings is set to “HSPA Normal” or “R99 only” (valid for FSMF only)
On SBTS level, the sum of existing PIC pools + activated NBIC LCGs needs to be lower
than or equal to four. Thus, the maximal number of supported NBIC LCGs depends on
the number of activated PIC pools as presented in the table below:
Table 23 Maximal supported SBTS configuration with NBIC and PIC (FSMF)
Number of PIC pools per SBTS Maximal number of supported NBIC LCGs
per SBTS
0 4
1 3
2 2
3 1
4 0
NBIC cannot be activated:
• In the LCG that has a mix of two way Rx Div cells and four way Rx Div cells
• In LCG with hspaSettings set to “HSPA Small”
Activation of NBIC in LCG requires static reservation of 0.5 SU for NBIC resource
processing. This 0.5 SU is used for NBIC processing and is not available for DCH,
HSUPA nor HS-RACH processing. The impact of NBIC activation on available baseband
capacity is presented in the table below:

Table 24 Number of subunits reserved from the LCG capacity after NBIC activation
(FSMF)
LCG HSPA settings (hspaSettings) Total cost in terms of static resource
consumption per LCG after NBIC activation
“HSPA Normal” 0.5 SU
“R99 only” 0.5 SU
Table 25 Number of subunits reserved from the LCG capacity after NBIC activation
(ASMI)
LCG SU Total cost in terms of static resource
consumption per LCG after NBIC activation
LCG with 4 subunits baseband capacity 1 SU
LCG with more than 4 subunits baseband 0.5 SU
capacity
Enhanced HSUPA interference cancellation feature dimensioning (PIC pools)

To achieve the high HSUPA throughput, these interference cancellation (IC) features are
recommended:
• RAN1308: HSUPA Interference Cancellation Receiver
• RAN2250: Enhanced HSUPA IC
RAN2250: Enhanced HSUPA IC requires RAN1308: HSUPA Interference Cancellation

Receiver. RAN2250: Enhanced HSUPA IC has no impact on baseband dimensioning.
The IC is performed with PIC pool units. With the picPool commissioning parameter,
the operator can activate the required number of PIC pools, and then perform cell
mapping to the PIC pools.
Four-way Rx Div is supported with the interference cancellation feature on FSMF or
ASMI, provided that the feature RAN3046: Interference Cancellation for 4RX is enabled.
Interference cancellation unit (PIC pool)
• Up to six cells with two-way Rx Div can be mapped to one PIC pool unit and
interference cancellation is performed in six cells at the same time.
• Up to three cells with four-way Rx Div can be mapped to one PIC pool unit and
interference cancellation is performed in three cells at the same time.
• Cells from the same frequency layer within the LCG should be mapped to the same
PIC pool unit.
• In ASMI, one PIC pool unit consumes one subunit capacity. PIC allocation excludes
CCCH pool allocation in the same group.
• In ASMI, only one PIC pool can be associated per baseband subunits group.
• In ASMI, each PIC activation excludes additional CCCH processing resources
allocation in grouped subunits.
Every PIC pool supports a mix of cells with different Rx Diversity.
General:

• Maximum four PIC pools in the SBTS
• Maximum six cells (two-way Rx) in the PIC pool
• Maximum three cells (four-way Rx) in the PIC pool
• Maximum three PIC pools per LCG
• Maximum two PIC pools per BB card (ABIA/FBBA/C cards)
PIC dimensioning details for Nokia AirScale BTS

If there are 32 Rxs or less (sum of Rxs from all WCDMA cells on the AirScale System
Module):
- Four PIC pools are allowed
If there are more than 32 Rxs (sum of Rxs from all WCDMA cells on AirScale System
Module):
- Two PIC pools and reduced third PIC pool (eight Rx – it means four cells two-way Rx
Div/four cells can be assigned to the third PIC pool)
High Speed Cell_FACH feature dimensioning

RAN1913: High Speed Cell_FACH (HS Cell_FACH UL) consumes baseband resources
for the HS Cell_FACH UL users processing. Using the
minNumOfHsRachResourceStepsRes and
maxNumOfHsRachResourceStepsRes parameters, the operator can define the
allocation of baseband resources for the HS Cell_FACH UL users. Baseband resources
allocation is done in steps:
• Up to eight steps are available for each LCG.
• Single step provides baseband capacity for 10 HS Cell_FACH UL users.
• Single step corresponds to the baseband capacity equivalent of single HSUPA
resource step: 0.125 su.
• A maximum of 80 HS Cell_FACH UL users can be served in the LCG, which
corresponds to eight HSUPA resource steps.
• If the RAN2518: High Speed Cell_FACH Enhanced feature is deactivated, up to four
steps can be effectively used (up to 40 HS Cell_FACH UL users). If RAN2518 is
activated, up to eight steps can be used (up to 80 HS Cell_FACH UL users).
• If the RAN3280: Dynamic Baseband for HS RACH is activated, the allocation of
baseband resources for HS Cell_FACH UL is done automatically and dynamically,
depending on the HS Cell_FACH UL traffic. This is done using the parameters
maxNumOfHsRachResourceStepsRes. At runtime, additional resources up to
maxNumOfHsRachResourceStepsRes are gradually allocated with resolution on
single HSUPA resource step. Allocation is triggered if already allocated baseband
resources are lower than the configured Common E-DCH resources for the HS
Cell_FACH UL users considering the number of preambles that are Not
Acknowledged (NACK-ed). Gradual release of resources down to
minNumOfHsRachResourceStepsRes with one HSUPA resource step resolution
is triggered based on the runtime resource usage when allocated baseband
resources capacity is higher than the average active amount of common E-DCH
resources. Both parameters can be modified online without SBTS reset.
• If the RAN3280: Dynamic Baseband for HS RACH is not active, the allocation of
baseband resources for the HS Cell_FACH UL is done statically and is not
dependent on the HS Cell_FACH UL traffic. This is done using the parameters

maxNumOfHsRachResourceStepsRes. In this case, both parameters have the
same value with one exception - the default values are different for both parameters:
minNumOfHsRachResourceStepsRes = 0 and
maxNumOfHsRachResourceStepsRes = 1.
The minNumOfHsRachResourceStepsRes parameter has a default value of 0 and
the maxNumOfHsRachResourceStepsRes has a default value of 1 (regardless of the
RAN3280: Dynamic Baseband for HS RACH activation status), which means that no
static baseband resource allocation is done. In this case, when the RNC is configuring
HS Cell_FACH UL user in the cell (it means Common E-DCH resources are reserved for
HS-Cell FACH UL cell), the SBTS attempts to dynamically allocate one HSUPA resource
step in the LCG for HS Cell_FACH UL users (supporting a maximum of 10 users in the
LCG). If the baseband capacity is available, one resource step is allocated for the HS
Cell_FACH UL. If the baseband capacity is not available, the HS Cell_FACH UL setup
from the RNC is rejected. RAN1637: High Speed Cell_FACH DL users do not require
any baseband resources reservation.
Dual Cell-HSUPA feature dimensioning
• Dual Cell HSUPA user is seen as two single carrier (SC) HSUPA users from the
maximum number of users per HSUPA scheduler. For example, with one DC-HSUPA
user, the HSUPA scheduler in the LCG supports a maximum of 618 SC-HSUPA
users.
• DC-HSUPA user is counted only in the primary cell from the Maximum number of
E-DCHs in the cell (MaxNumberEDCHCell) point of view.
• DC-HSUPA user is counted only once per LCG from the Maximum number of E-
DCHsin the LCG (MaxNumberEDCHLCG) point of view.
• Single LCG configuration supports up to 310 DC-HSUPA users in the LCG.
• Both DC-HSUPA cells need to be within the same LCG.
• Up to 10 DC-HSUPA users are supported per cell.
• DC-HSUPA operation is supported only with F-DPCH and 2ms TTI.
• DC-HSUPA user is seen as two SC-HSUPA users from the HSUPA resource
consumption point of view. In Flexi Multiradio 10 BTS and Nokia AirScale BTS
HSUPA capacity tables:
– The column “HSUPA users per scheduler” defines SC-HSUPA users, thus one
DC-HSUPA user is counted as two SC-HSUPA users
– The row “Baseband minimum decoding capacity” defines the capacity that the
SBTS shares for all the cells in the LCG
• RAN3067 Flexible HSDPA Carriers Allocation and RAN1905 DC-HSUPA cannot be

enabled simultaneously
HSUPA 16QAM feature dimensioning

Up to three UEs transmitting with 16 QAM modulation can be allocated in one subunit as
presented in the table below.
Table 26 Up to three HSUPA UEs with 16QAM transmission can be allocated in a
single subunit in the FSMF
Number of HSUPA 16QAM transmitting Required subunits (FSMF)
users
1 0.375*

Table 26 Up to three HSUPA UEs with 16QAM transmission can be allocated in a
single subunit in the FSMF (Cont.)
Number of HSUPA 16QAM transmitting Required subunits (FSMF)
users
2 0.625
3 0.875
g Note: *One 16QAM UE consumes 0.375 SU with throughput >= 4.2 Mbps and up to
11Mbps. 16QAM is not used with throughput < 4.2 Mbps. In this case, dimensioning is
done based on HSUPA dimensioning tables (
Flexi Multiradio 10 BTS and Nokia AirScale BTS HSUPA capacity tables).
Subunit utilization can change on TTI base. In the first TTI, the UE transmits with
16QAM modulation. In the second TTI, different modulation can be used, depending on
the radio conditions or the amount of data in the UE buffer.
2.2.9 Multi RAB

A call of a single user with multiple (up to four) services active simultaneously is a multi
RAB call. For example, a UE actively downloading data via the HSDPA service while
having simultaneous AMR voice call, has a multi RAB service with two RABs
established: HSDPA RAB + AMR RAB. General classification of multi RAB calls is as
follows:
• HSDPA + AMR call
• HSUPA + AMR call
• HSUPA/HSDPA + HSUPA/HSDPA call
• DCH + DCH call
HSPA + AMR call resource allocation

If AMR DCH service is established while the UE has an active HSPA connection, the
AMR service is processed with already allocated HSUPA resources. AMR service of
multi RAB call does not require any additional baseband resources for processing,
neither Rel.99 CE LKs are required in UL/DL.
Setup of an AMR service with ongoing HSPA connection may have an impact on
available baseband resources, depending if the F-DPCH feature is actively used by the
UE:
• HSPA non-FDPCH connection: the newly established AMR service of multi RAB call
does not have any impact on available baseband resources
• HSPA FDPCH connection: if AMR service of multi RAB call is newly set up, the
HSUPA connection is considered as HSUPA non-FDPCH from the baseband
resource consumption point of view
DCH + DCH call resource allocation

Each DCH service of a multi RAB call requires separate Rel.99 CE baseband resources
in UL/DL for processing. In case of a multi RAB call, an equivalent amount of Rel. 99CEs
is consumed as in case of separate DCH single RAB calls.

For example, 64/64kbps + 64/128kbps multi RAB baseband resource reservation is the
same as baseband resource reservation for 64/64kbps and 64/128kbps single RABs.
2.3 LTE baseband dimensioning in SBTS

For information on LTE baseband dimensioning in SBTS, see FDD-LTE Radio
Dimensioning Guideline, Baseband dimensioning and SBTS Supported Configurations.

SBTS Dimensioning Common transport dimensioning in SBTS
3 Common transport dimensioning in SBTS

How to dimension the common transport network in SBTS.
3.1 SBTS common transport dimensioning process

Single RAN introduced the concept of common transport. Instead of having one transport
for each RAT, there is only one shared transport entity in SBTS.
Network load is calculated separately for each RAT. Total network load is calculated as a
sum of loads of GSM, WCDMA and LTE technologies. GSM is treated as a fallback for
WCDMA in terms of voice services.
There are two possible approaches to common transport dimensioning in SBTS:
• Based on traffic profile (recommended)
• Based on air interface capabilities
Figure 23 Approaches to SBTS common transport dimensioning
Throughput
HSPA HSPA LTE

evo
basedontrafficprofile basedonairinterfacecapacity
Transport capacity
3.2 Dimensioning based on traffic profile

(recommended)
Dimensioning based on traffic profile has the following benefits:
• It is tailored to actual needs.
• It allows the Quality of Service (QoS) parameters to be taken into account.
A traffic profile needs to be provided by the operator. If a traffic profile is not available, a
default Nokia traffic profile can be used as a substitution. However, Nokia default traffic
profile is not the same as a customer traffic profile.

Common transport dimensioning in SBTS SBTS Dimensioning
3.3 Dimensioning based on air interface capabilities

Dimensioning based on air interface capabilities has the following benefits:
• It is a simple and straightforward calculation.
• It can be used if a traffic profile is not available.
There are three approaches to perform dimensioning based on air interface capabilities,
each based on different assumptions:
• All-Average
The backhaul connection supports the aggregated average capacity of all cells. The
average capacity is determined under realistic air interface conditions and multiple
users per cell.
• All-Average/Single-Peak
The backhaul connection supports the aggregated average capacity of all cells or the
peak capacity of one cell (whichever has the greater value).
• All-Peak
The backhaul connection supports the aggregated peak capacity of all cells. The
peak capacity is determined under ideal air interface conditions and with a single
user per cell. This approach leads to over-dimensioning, which usually generates
extra costs.
Figure 24 Approaches based on air interface capabilities
Air interface Transport
capacity capacity
Theoretical Maximum
(over dimensioning)
Recommended dimensioning range
practical
maximum
overbooking
minimum
All-average/ All-but-one-Average/ All-Peak

Cell peak Cell All-Average Single-Peak Single-Peak ∑ peak
Average ( ∑ average ) MAX(( ∑ average), cell peak, UE peak) (2 x average + 1 peak)
This figure presents the recommended dimensioning range. As an example, a three-
sector base station is used. However, it is scalable to base stations having more than
three sectors.
The All-Average/Single-Peak approach is a good way to optimize both performance and
costs. However, it may lead to over-dimensioning for sites with low utilization, and under-
dimensioning for hot spots.

Figure 25 Dimensioning based on air interface capacity with carrier aggregation
2 CC Carrier Aggregation (UE peak equals 2x cell peak)
Theoretical Maximum
Air interface capacity Transport capacity (over dimensioning)
Recommended dimensioning range
Overbooking
Cell peak
Cell
average
All-Average All-average/ All-but-one-Average/ All-Peak

3 sector eNB as example Single-Peak Single-Peak S peak
S average
(can be scaled up for bigger sites)
MAX(( S average), cell peak, UE peak) 2 x peak + 1 x average
The carrier aggregation introduces the UE peak. At least, a single UE peak needs to be
transported via the backhaul network. This peak is determined by the sum of carriers
being aggregated (as the two carriers shown in the figure above).
LTE3022/SR001419: Inter-site Carrier Aggregation feature extends the existing carrier
aggregation functionality by allowing the aggregation of additional secondary cells
(SCells) hosted by remote eNBs/SBTSs connected over the X2 interface.
Inter-site carrier aggregation (I-S CA) is possible only in downlink, and for a maximum of
five component carriers (CC) in the FDD mode or for maximum four CCs in the mixed
mode (2 FDD + 2 TDD). The maximum number of eNBs/SBTSs involved in a single I-S
CA operation is four.
Due to I-S CA, there is additional traffic observed on the S1 interface (PCell) and on the
X2 interfaces. The interface dimensioning needs to consider this extra traffic.
The traffic split among the CCs in downlink is realized in the master eNB/SBTS (that is
the one hosting the primary cell (PCell)) by the data scheduler. The entire traffic due to I-
S CA is processed first in the master eNB/SBTS before it gets dispatched to the other
eNBs/SBTSs over the X2 interface.

Figure 26 Inter-site carrier aggregation
EPC - user data (S1/X2)

- user data (Radio)
S1
X2 eNB
eNB
eNB/SBTS eNB/SBTS
PCell SCell SCell SCell
4CC I-S CA UE
g Note: Carrier Aggregation- In radio resource management, a method of increasing the
bit rate by increasing the bandwidth. It is done by scheduling the data package transfer
to more than one cell (component carriers). In CA, one cell acts as a primary cell and is
changed only during the handover process, while the other component carriers are
served by secondary cells and can be added or removed as required.
Component Carrier- In carrier aggregation, the part of transmission bandwidth. The
component carriers can belong to the same band (intra-band CA) or be parts of
different bands (inter-band CA).
Primary Cell- In carrier aggregation, the cell that is used to configure the connection.
The PCell hosts radio resource control protocol data connection in addition to providing
an additional bandwidth for increasing the bit rate. The PCell for the UE is changed only
at handover.
Secondary Cell- In carrier aggregation, the additional cell that hosts a component
carrier. The SCell provides an additional bandwidth for increasing the bit rate. The SCell
for the UE can be added or removed when required.
The eNB/SBTS that is chosen as PCell is facing additional traffic in downlink (S1-U) and
uplink (X2-U). The SCell's total downlink traffic does not change, as well as the I-S CA
traffic for total cell capacity. As such, the total amount of SCell traffic is just moving from
S1-U to a sum of S1-U and X2-U. The selection of the PCell is also distributed across
the eNB/SBTS and the expected percentage of I-S CA calls is fairly moderate. This

results in an increase of the total downlink and uplink traffic, however, not to a significant
amount. Precise dimensioning can be done only by taking into account several
assumptions and configuration parameters.
3.4 Transport overhead and dimensioning example

When calculating network load, air interface overhead and transport overhead need to
be taken into account. Typically, transport overhead amounts to 27% of packet size
increase, 2% of which results from air interface overhead. If IPsec is not in use, transport
overhead amounts to 15%.
g Note: The overhead depends on the average packet size that might vary from traffic
profile to traffic profile.
Figure 27 Example of SBTS common transport dimensioning based on air interface
capabilities without LTE carrier aggregation
Singlecellpeak+25%
25
25
25 31
75
75 94
75
BTS MAX(3xaverage;peakrate)
Airinterfaces Tranportinterface
Transport in downlink direction:
• 75 Mbit/s net PHY peak rate per cell (64QAM 2x2 MIMO)
• 17 Mbit/s net PHY average rate per cell
Transport in uplink direction:
• 25 Mbit/s net PHY peak rate per cell (16QAM)
• 7 Mbit/s net PHY average rate per cell
Transport overhead (Ethernet layer, with IPsec):
• Air interface overhead (PDCP/RLC) -2%
• Transport overhead (GTP-U, UDP, IPv4, Eht) +15%
• IPsec overhead: +12%
_________________________________________________
• Total (on top air interface capacity) +25%
MAX((Σ average), cell peak, UE peak) = MAX(3 * 7; 25) = 25 Mbit/s
MAX((Σ average), cell peak, UE peak) = MAX(3 * 17; 75) = 75 Mbit/s
25 * (1+0.25) = 31 Mbit/s

75 * (1+0.25) = 94 Mbit/s
In case carrier aggregation is used, the possible UE peak exceeds the cell peak, since
several cells' peaks are combined.
3.5 Estimation of C/M/S-Planes bit rate

Control Plane (C-Plane) bit rate:
• Depends on user activity and mobility.
• During calculation, only the simplest method is taken into account:
TransportCapacityC-Plane[kbit/s] = TransportCapacityU-Plane[kbit/s] * C-
PlaneBWPercentage[%]
Default values for C-PlaneBWPercentage:
– LTE = 1%
– WCDMA = 6%
Management Plane (M-Plane) bit rate:
• Mainly depends on counter and tracing configuration.
• Peaks may reach up to 30 Mbit/s. However, only a small part (0-5 Mbit/s) is needed
on permanent basis.
Recommended bandwidth from transport dimensioning perspective:
– LTE = 1 Mbit/s
– WCDMA = 64 kbit/s
– GSM = 64 kbit/s
Synchronization Plane (S-Plane) bit rate:
• Depends on the selected synchronization method:
– Timing over Packet (ToP) with frequency synchronization = ~16 kbps/site (at 16
msgs/second)
– Timing over Packet (ToP) with phase synchronization = ~239 kbps/site (at 128
msgs/second)
– Synchronous Ethernet (SynchE) = ~8kbps/site (SSM messaging)
3.6 Mutliplexing gain

Multiplexing gain is the amount of transport link bandwidth (BW) that can be saved by
considering the diversity of the traffic demand, that is the variation of the traffic load in
time and the available buffering space.

Figure 28 Calculation of the multiplexing gain
Aggregation
Aggregation
CoreNEs
Corerouters
Siterouters
BTSs
multiplexing_gain= ( 1-
Aggregated_TN_BW
BW_BTS1+BW_BTS2 ( x100%
The figure presents multiplexing gain on the transport network between two radio cells
(LTE and HSDPA).
Multiplexing gain decreases as cell load increases.

Figure 29 LTE and HSDPA cells load multiplexing gain
40
multiplexinggain[%]
30
20
10
0
1 2 3 4 5 6 7 8
LTEandHSDPA cellload[Mbps]
For details on WCDMA access network dimensioning, see Dimensioning WCDMA RAN:
Access Network (Transport Interfaces).
For details on LTE access network dimensioning, see LTE Access Dimensioning
Guideline.

SBTS Dimensioning SRAN capacity licenses
4 SRAN capacity licenses

License management is a method for controlling the use of optional software
applications, the capacity of network elements, and some optional hardware
functionalities. For more details, see Single RAN License Operation.
SRAN capacity licensing is based on air interface traffic and backhaul transport traffic.
The air interface traffic licenses are:
• SR001004.T SBTS Data User
• RAN2123.4.T R99 CE capacity
• RAN2123.6.T CCCH Processing Set
• BSC00311 Flexi Multiradio TRX HW activation license
Backhaul transport traffic is covered by the licenses introduced by SR000834: IP Traffic
Capacity feature. There are three options available. The operator can choose only one at
a time. The options are mutually exclusive.
Backhaul transport traffic licenses are:
• SR000834.1.T SBTS Daily UP Data Volume
• SR000834.3.T SBTS Quarterly UP Data Volume
• SR000834.2.T SBTS Busy Hour UP Throughput

Single RAN, Rel. SRAN 18 SP, Operating Documentation, Issue 01

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Single RAN, Rel. SRAN 18 SP, Operating Documentation, Issue 01

Uploaded by

Copyright:

Available Formats

Single RAN, Rel.

f Important Notice on Product Safety

1 Overview of the SBTS dimensioning

1.1 Dimensioning and capacity

1.2 SBTS System Modules

GSM LTE TRS

GSM WCDMA TRS

AirScale System Module

half subrack half subrack

Flexi 10 BTS System Module AirScale System Module

One logical SBTS

1.3 Cell sets

1.4 Common transport

2.1 GSM baseband dimensioning in SBTS

2.2 WCDMA baseband dimensioning in SBTS

2.2.1 Flexi Multiradio 10 BTS

g Note: RAN3017: Additional 6 WCDMA cells activation feature license key(s) are

For supported configurations, see SBTS Supported Configurations and Creating SBTS

2.2.2 Fundamentals of Flexi Multiradio 10 BTS baseband

Flexi 10 BTS System Module available capacity

OptionalHSUPA staticallocationsubunits(0) CommissionedresourcesforHSUPA

Rel.99 CE System Module capacity

2.2.3 Nokia AirScale BTS

ASIA (Common PIU)

2.2.4 Fundamentals of Nokia AirScale BTS baseband

AirScale System Module sharing

4 su (0,5xABIA) 2,875 su 220 154 276

2.2.5 Common Control Channels dimensioning

The extended cell

CCCH dimensioning details

CCCH resources in FSMF

CCCH resources allocation

Example: BB capacity distribution in LCGs

Required CCCH resources for basic configurations

Small HSPA Local Cell Group

2.2.6 Dedicated channels (DCH) dimensioning

RAB Traffic CS /PS Max Min SF Min SF Required Required

AMR Conversat CS 1.2 64 128 1 1

RAB Traffic CS /PS Max Min SF Min SF Required Required

Packet Interactive PS 16 64 128 1 1

Asymmetric UL/DL R99 CE allocation

2.2.7 HSDPA dimensioning

HSDPA, DC/DB-HSDPA, RAN3067: Flexible HSDPA Carriers Allocation: Carrier

Multi RAB users

HSDPA Rel.99 CE consumption for A-DCH and DL SRB

Associated UL/DL DCH

Table 20 Tcell values handled by HSDPA schedulers (Flexi Multiradio 10 BTS)

DB/DC-HSDPA Tcell settings

12HSDPA cells,DCHSDPA activated, 12HSDPA cells,DCHSDPA not activated,

Ff1 DC-HSDPA Ff1

12HSDPA cells, 2HSDPA schedulersactivated, 12HSDPA cells, 2HSDPA schedulersactivated,

Ff1 Tcell=0 Tcell=1 Tcell=2 Ff1 Tcell=0 Tcell=1 Tcell=2

Ff2 Tcell=0 Tcell=1 Tcell=2 Ff2 Tcell=6 Tcell=7 Tcell=8

Ff3 Tcell=3 Tcell=4 Tcell=5 Ff3 Tcell=3 Tcell=4 Tcell=5

Ff4 Tcell=3 Tcell=4 Tcell=5 Ff4 Tcell=3 Tcell=4 Tcell=5

CA DB/DC-HSDPA Tcell settings

Table 22 Tcell values handled by HSDPA schedulers when RAN3067: Flexible

Tcell Values from Group 11 0, 1, 2 N/A

Tcell Values from Group 22 N/A 3, 4, 5

Tcell Values from Group 33 6, 7, 8 N/A

Simultaneous HSDPA users in TTI

With the RAN3269: Optimized HSDPA Scheduler feature, the scheduler supports up to

2.2.8 HSUPA dimensioning

OptionalHSUPA staticallocationsubunits(0) CommissionedresourcesforHSUPA

12HSDPA cells,DCHSDPA activated, 12HSDPA cells,DCHSDPA not activated,

12HSDPA cells, 2HSDPA schedulersactivated, 12HSDPA cells, 2HSDPA schedulersactivated,