77
1 © Nokia Siemens Networks RU30 BaseBand dimensioning rules Company Confidential RU30 BaseBand dimensioning rules Network Engineering NWS LTE RA E2E SA NE WCDA !"#0"#20!!

RU30 BB Dim Planning

Embed Size (px)

DESCRIPTION

RU30 Planning

Citation preview

Network Planning Info NetEng

RU30 BaseBand dimensioning rulesNetwork Engineering NWS LTE RA E2E SA NE WCDMA14.04.2011# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential1ContentsGeneral BaseBand dimensioning rules in RU30RU30 Licensing aspectsHSDPA in RU30Common Control Channels allocation rulesLocal Cell GroupingHSDPA BTS processing set resource allocationRU30 HW/SW description - Flexi WCDMA BTS and UltraSite WCDMA BTSHSUPA in RU30HSUPA BTS processing set resource allocationBackup slidesCS Voice over HSPA# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential2General dimensioning rules in RU30# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential3No changes: For pure Flexi System Module Rel.1 (FSMB) baseband dimensioning

For UltraSite (WSPA/WSPC) and EUBB (WSPF) baseband dimensioning

EUBB supported on RU20 On Top SW level

In R99 dimensioning rules

General dimensioning rules in RU30 (1/2)Changes: New licensing aspects for Flexi System Module Rel.2 Rel99 CE licenses HSDPA/HSUPA BTS processing sets New rules for HSPA baseband dimensioning

# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential4Processing capability of System Module Rel.2 is significantly increased comparing to RU10/RU20

Common Control Channels dimensioning is similar as in RU10/RU20 Basic configurations (3cells/20km or 6cells/10km) are supported with baseband resources included in System Module Rel.2 capacity 48 Rel99 CE licenses are required per each step

HSPA dimensioning approach changes in comparison to RU10/RU20 BTS processing steps are introduced (HSPA does not consume CE licenses any more) HSDPA/HSUPA performance (throughputs, number of active users) improvement

R99 dimensioning same as in RU20 On Top Rel99 CE consumption same as in RU20 On Top

General dimensioning rules in RU30 (2/2)# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential5RU30 Licensing aspects# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential6Licensing aspects (1/8)General informationRU30 Licensing aspectsNo changes in Flexi HW Rel.1 CE license conceptIn RU30 for Flexi System Module Rel.2 CE license is valid for R99 trafficHSDPA and HSUPA schedulers (System Module rel.2) do not consume CE licensesHSDPA/HSUPA will have own capacity licenses that are called respectively HSDPA BTS processing sets and HSUPA BTS processing set# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential7Licensing aspects (2/8)Rel99 CE licenses Supported only by Flexi System Module Rel.1 and Rel.2

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

System Module rel.2 HSPA schedulers do not anymore consume R99 CE licenses (except A-DCH and SRB resources if needed)

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

HSPA schedulers allocated at System Module rel.1 still consume CE licenses (called in RU30 - R99 CE licenses)Rel99 CE licenses# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential8Licensing aspects (3/8)General informationRU30 Licensing aspectsCE licenses consumption: CCCH resources (if needed e.g. extended cell case) R99 users (PS and CS services) A-DCH (Associated DCH) SRB (if needed*)* HSDPA service (UL:R99 bearer, DL:HSDPA bearer) - 1 Rel99 CE in DL per user needed; HSUPA data service (UL:HSUPA bearer, DL:HSDPA bearer) no CE licenses needed

HSUPA voice service (UL:HSUPA bearer, DL:HSDPA bearer) FDPCH required (no CE licenses required) # Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential9Licensing aspects (4/8)HSDPA BTS processing setIt is capacity reservation inside the System Module Rel.2 that allows allocate certain amount of HSDPA users and DL throughput

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

Customers can put freely set 1 licenses or set 2 and set 3 licenses for increasing licensed HSDPA throughput and maximum HSDPA user amount HSDPA BTS processing set licenses are incremental as R99 CE licenses. Note: HSDPA processing set 1 licenses are always included into sets 2 and 3. E.g. when set 2 is bought maximum capacity is as set 2 defines (set 1 capacity is not summed into set 2)

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

Processing set does not guarantee the maximum user amount and throughput but additional features are needed e.g. 64-QAM, 10/15 HS-PDSCH codes, 72HSPA users per cellHSDPA BTS processing set# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential10Only shared scheduler license is not used in RU30 anymoreLicensing aspects (5/8)HSDPA BTS processing setHSDPA processing setMax number of HSDPA users per BTSMax HSDPA throughput per BTSHSDPA BTS processing set 1327,2 MbpsHSDPA BTS processing set 27221 MbpsHSDPA BTS processing set 37284 MbpsOperator can activate combination of different HSDPA processing sets

e.g. 2 x HSDPA BTS processing set 2 + 1 x HSDPA BTS processing set 3 = 2* 72 UEs / 2* 21Mbps + 1*72 UEs / 1*84Mbps = 216 UEs / 126Mbps# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential11Licensing aspects (6/8)HSUPA BTS processing setHSUPA BTS processing setHSUPA BTS processing set is capacity reservation inside the Rel.2 HW that allows allocated certain amount of HSUPA users and UL throughput.One type of HSUPA BTS processing set license with capacity of 24 HSUPA UEs or 5,8Mbps throughput with one UE is availableR99 UEs can be allocated into HSUPA processing set 1 even there is no R99 CE license (1/2 subunit = 24 Rel.99 CE)HSUPA BTS processing set does not enable peak UL throughputs, but it can limit those (as HSDPA BTS processing set does for DL throughput). For achieving peak UL throughputs customer needs to buy separate license for peak throughput features like HSUPA 16QAM.# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential12Licensing aspects (7/8)HSUPA BTS processing setHSUPA processing setMax number of HSUPA users per BTSMax HSUPA throughput per BTSHSUPA BTS processing set 1245,8 MbpsOperator can activate a few HSUPA processing sets

e.g. 6 x HSUPA BTS processing set 1 (6*24 UEs = 144 UEs per BTS, 6*5,8 Mbps = 34,8 Mbps)# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential13Licensing aspects (8/8)HSPA BTS processing set summary HSDPA BTS processing set 1: 32 users and 7.2MbpsHSDPA BTS processing set 2: 72 users and 21MbpsHSDPA BTS processing set 3: 72 users and 84MbpsHSUPA BTS processing set 1: 24 users and 5.8MbpsNote: HSUPA maximum air interface throughput is achieved with one user. License does not guarantee maximum throughput for maximum amount of users. If maximum amount of users is reached the throughput is minimal.

Above HSDPA throughputs are peak air interface throughputs of BTS. HSDPA BTS processing sets throughput is maximum throughput per SMHSPA BTS processing set capacities# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential14Baseband allocation processDynamic allocated resources according to traffic demandStatic allocated resources based on available configuration and commissioning # Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialHW in RU30 Flexi WCDMA BTS rel.2# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential16In RU30 following Flexi System Modules are available: FSMB System Module (Rel.1 HW) FSMC System Module (Rel.2 HW) FSMD System Module (Rel.2 HW) FSME System Module (Rel.2 HW)

Number of commissioned Interference Cancellation units (PIC pool)HW in RU30 Flexi WCDMA BTS (1/12)RU30 System Module Rel.2 BB capacity for traffic use depends on: HSDPA commissioned resources Number of cells commissioned to System Module Rel.2# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential17BaseBand resources allocation (2/12) System Module rel.2 capacity System Module Rel.2 consist of certain number of processing subunits. Each subunit can provide R99 processing resources (R99 CE), HSDPA processing resources (HSDPA users and throughput) and HSUPA processing resources (HSUPA users and throughput). Additionally each unit can be used for CCCH processing (e.g. extended cell case) or work as interference calculation unit.

In certain cases (i.e. overlapping) subunits are able to process R99 users and provide HSUPA processing resources.R99 CEHSUPA thr., usersHSDPA thr., users, HSDPA cellsR99 CEHSUPA thr., usersExemplary figuresHSDPA thr., users, HSDPA cells1 subunit# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialBaseBand resources allocation (3/12) System Module rel.2 logical structureRU20 System Module rel.2 consists of CECEExemplary figuresR99 CEHSUPA thr., usersHSDPA thr., users, HSDPA cellsR99 CEHSUPA thr., usersExemplary figuresHSDPA thr., users, HSDPA cells1 subunitRU30 System Module rel.2 consists of subunits that provides different functions according to available licensesCECECECE-> SM capacity referred in CE-> SM capacity can be referred in:R99 CEHSDPA thr, users and cellsHSUPA thr and users# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential19HW in RU30 Flexi WCDMA BTS (4/12)System Module Rel.2 capacity - number of cellsSystem Module Rel.2 RU30 subunits capacity depends on number of commissioned cells. Formula below can be used to calculate number of available subunits for traffic use (or CCCH / interference cancellation processing)Where:Number of subunits:FSMC=6FSMD=13FSME=20Number of available subunits = Number of subunits roundup (Number of cells / 3))Available resources (subunits) can be used for CCCH processing, HSDPA users, thr. and cells processing, HSUPA users and thr. processing, R99 users processing and interference cancellation processingPlease note that each SM Rel.2 contains CCCH processing resources required for Basic Configurations (e.g. 6 cells/10km or 3cells 20km) included in system module capacity# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential20Number of available subunits for different cell configurations:Number of cellsNumber of subunitsFSMCFSMDFSME1 3512194 6411187 92 + 1*9 + 1*16 + 1*10 121 + 1*8 + 1*15 + 1*+1*Additional subunit for CCCH resources needed if one System Module and more than 6 cells Additional CCCH resources are not required if two System Modules(cell range up to 10km / 2-way Rx diversity assumed)Examples when two System Modules:1)FSME + FSME / 1 LCG, 12 cells/10km: Number of subunits = 16 + 16 32 subunits available2) FSME (LCG1: 6cells/10km) + FSME (LCG2: 6cells/10km) Number of subunits = 18 + 18 36 subunits available3)FSMD + FSME / 1 LCG, 12 cells/10km: Number of subunits = 9 + 16 25 subunits available

HW in RU30 Flexi WCDMA BTS (5/12)System Module Rel.2 capacity HSDPA not activated# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential21Please note that for 1-3 and 7-9 cells cell range up to 20km can be assumed while for 4-6 and 10-12 cells up to 10km cell range can be assumed

HW in RU30 Flexi WCDMA BTS (6/12)System Module Rel.2 capacity - number of cellsFormula below can be used to calculate the maximum Rel99 System Module Rel.2 capacity (Rel99 CE)Number_of available_subunits = (Number of subunits roundup (Number of cells / 3) HSDPA_subunits PIC_pool_subunits)System Module Rel99 CE capacity = min( #Rel99CE_licenses ; (Rel99_CE_Subunit_capacity * Number_of_available_subunits))Where:HSDPA_subunits subunits dedicated for HSDPA purpose PIC_pool_subunits number of interference cancellation unitsWhere:#Rel99CE_licenses number of available CE licenses Rel99_CE_subunit_capacity Rel99 CE subunit capacity (48 Rel99 CE)# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential22HW in RU30 Flexi WCDMA BTS (7/12)System Module Rel.2 capacityNumber of cellsFSMCFSMDFSMERU20RU30RU20RU30RU20RU301 3180 CE240 Rel99 CE396 CE576 Rel99 CE612 CE912 Rel99 CE4 6180 CE192 Rel99 CE396 CE528 Rel99 CE612 CE864 Rel99 CE7 9144 CE96 Rel99 CE360 CE432 Rel99 CE576 CE768 Rel99 CE10 12144 CE48 Rel99 CE360 CE384 Rel99 CE576 CE720 Rel99 CE Up to 33% higher capacityUp to 45% higher capacityUp to 49% higher capacityIn the table below System Module Rel.2 SW Rel99 CE capacity for pure traffic is presented (HSDPA not activated)One FSMC supporting more than 6 cells foreseen for low load scenarios10km cell range assumedPlease note that presented in the table above SM rel.2 capacity can be observed in the max available Rel99 CE counter if appropriate number of Rel99 CE licenses is available.# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential23Please note that for 1-3 and 7-9 cells cell range up to 20km can be assumed while for 4-6 and 10-12 cells up to 10km cell range can be assumed

HW in RU30 Flexi WCDMA BTS (8/12)System Module Rel.2 capacity HSDPA activatedMaximum HSDPA throughput for System Module Rel.2 HSDPA baseband capacity(HSDPA throughput subunits) 0 MbpsHSDPA schedulers not activated84 Mbps2168 Mbps3252 Mbps4336 Mbps5420 Mbps6504 Mbps7In order to achieve certain HSDPA throughput appropriate baseband resources need to be allocated for HSDPA purpose.Up to two HSDPA schedulers can be activated at one System Module Rel.2. Please note that HSDPA baseband capacity is common for both schedulers. HSDPA_subunits = HSDPA_throughput_subunits + Number_of_LCGs * 1/4Where: Number_of_LCG = number of LCGs covering System Module rel2 BB capacity# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential24HW in RU30 Flexi WCDMA BTS (9/12)System Module Rel.2 capacity HSDPA activatedThe max R99 CE capacity of System Module Rel.2 with HSDPA service activated (at least one HSDPA scheduler activated) can be calculated from the formula below (HSUPA not activated):Number of cellsFSMCFSMDFSME1 3132 Rel99 CE468 Rel99 CE804 Rel99 CE4 684 Rel99 CE420 Rel99 CE756 Rel99 CE7 9N/A324 Rel99 CE660 Rel99 CE10 12N/A276 Rel99 CE612 Rel99 CE10km cell range assumed, 1 LCG covers SM rel.2 capacity, up to 3 HSPA (MIMO) cells or 6 HSPA (non-MIMO) cell assumed System Module R99 CE capacity = R99_CE_Subunit_capacity * (Number_of_subunits roundup (Number of cells / 3) HSDPA_subunits)In the table below System Module Rel.2 R99 CE capacity for pure traffic is presented with HSDPA service activation (HSDPA thr. up to 84Mbps)# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential25Please note that for 1-3 and 7-9 cells cell range up to 20km can be assumed while for 4-6 and 10-12 cells up to 10km cell range can be assumed

HW in RU30 Flexi WCDMA BTS (10/12)System Module Rel.2 capacity HSUPA activated HSUPA activation does not consume any baseband resources. However for HSUPA users and throughput processing baseband resources (subunits) needs to be allocated based on current traffic need. HSUPA baseband resources allocation is performed in steps so called HSUPA resource steps. One step is equal to of System Module rel.2 subunit. HSUPA baseband capacity reservation is based on HSUPA license (HSUPA BTS processing sets) In case if R99 CE licensed baseband resources are overlapping HSUPA licensed baseband resources overlapped resources can be dynamically exchanged between R99 and HSUPA users One HSUPA BTS processing set license requires 2 HSUPA resource steps (1/2 subunit) # Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential26HW in RU30 Flexi WCDMA BTS (11/12)Interference cancellation units In case when Interference Cancellation feature is activated, Interference Cancellation units (PIC pool) needs to be commissioned in order to perform interference cancellation for mapped HSPA cells. One PIC pool requires one subunit. Number of PIC pool is commissioned by operator One PIC supports up to 6 cells (interference cancellation can be done simultaneously in 3 selected by BTS cells) Cells from one frequency layer should be mapped to one PIC pool One PIC pool supports up to 2 frequency layers

# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential27Please note that for 1-3 and 7-9 cells cell range up to 20km can be assumed while for 4-6 and 10-12 cells up to 10km cell range can be assumed

Number of PIC poolNumber of cellsFSMCFSMDFSME11 - 384 Rel99 CE420 Rel99 CE756 Rel99 CE4 636 Rel99 CE372 Rel99 CE708 Rel99 CE7 9N/A276 Rel99 CE612 Rel99 CE10 - 12N/A228 Rel99 CE564 Rel99 CE21 - 336 Rel99 CE372 Rel99 CE708 Rel99 CE4 - 6N/A324 Rel99 CE660 Rel99 CE7 - 9N/A228 Rel99 CE564 Rel99 CE10 - 12N/A180 Rel99 CE516 Rel99 CERemark: HSDPA service is activated (up to 84 Mbps per System Module without additional baseband resources)Max System Module R99 CE capacity = R99_CE_Subunit_capacity * (Number of subunits roundup (Number of cells / 3) HSDPA_subunits #PIC_pool_units)The max R99 CE capacity of System Module rel.2 with HSDPA service activated and PIC pools can be calculated from formula below.The max R99 CE capacity of System Module rel.2 with HSDPA service activated (up to 84Mbps) and PIC pools can be seen in the table belowHW in RU30 Flexi WCDMA BTS (11/12)Interference cancellation units10km cell range assumed, 1 LCG covers SM rel.2 capacity, up to 3 HSPA (MIMO) cells or 6 HSPA (non-MIMO) cell assumed # Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialLocal Cell Grouping# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential29Local Cell Grouping (1/5)RU30In release WBTS7.0 Local Cell grouping for Flexi BTS is needed in a case of more than 6 cells are configured per BTS with at least one HW Rel.1 (System Module or RF module) or if more than two cells areconfigured usingAntenna 1 and Antenna 3for cell from sameRelease1 dual radio module.

In RU30 single LCG covers up to 12 cells with pure Release 2 HW configuration (System Module + RF module). However when 4 Way Rx diversity is used, up to 6 cells with 4 way RX diversity can be dedicated to one LCG. In release WBTS7.0 Local Cell grouping for Flexi BTS is needed in a case of more than 6 cells are configured per BTS with at least one HW Rel.1 (System Module or RF module) or if more than two cells areconfigured usingAntenna 1 and Antenna 3for cell from sameRelease1 dual radio module.RU30RU20 on TopNEW# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential30Local Cell Grouping (2/5)Interference Cancellation featureRU30When Interference Cancellation feature is used (System Module Rel.2 required) only one LCG can be created with one System Module Rel.2

When Interference Cancellation feature is used (System Module Rel.2 required) up to two LCGs can be created with two System Modules Rel.2. In this case BaseBand capacity is shared between LCGs according to the system module capacity (LCG1: Master System Module, LCG2: Extension System Module)

SM Rel. 2(FSMC/FSMD/FSME)LCG 1Master SM Rel. 2(FSMC/FSMD/FSME) LCG1Extension SM Rel. 2(FSMC/FSMD/FSME)LCG2PICPICMaster SM Rel. 2(FSMC/FSMD/FSME) LCG1Extension SM Rel. 2(FSMC/FSMD/FSME)PICMaster SM Rel. 2(FSMC/FSMD/FSME) LCG1Extension SM Rel. 2(FSMC/FSMD/FSME)PICPICLCG2Master SM Rel. 2(FSMC/FSMD/FSME) LCG1Extension SM Rel. 2(FSMC/FSMD/FSME)PICPIC# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential31Local Cell Grouping (3/5)LCG configuration and BTS capacityFSME FSME 12 cells are served by LCGFSME FSME 6 cells are served by LCG16 cells are served by LCG22x768=1536 Rel99 CE SW capacity is available2x864=1728 Rel99 CE SW capacity is availableBaseBand resources can be utilize freely by traffic from all carriersHigher BTS capacity is available FSME FSME 9 cells are served by LCG13 cells are served by LCG21x816 (48 Rel99 CE for CCCH required) + 1x768 = 1632 Rel99 CE SW capacity is availableSM#1 serves 9 cells from LCG1SM#2 serves 9 cells from LCG1 and 3 cells from LCG2 so 9+3=12 cells Example assumes that HSDPA is not activated, cell rage up to 10km# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential32Local Cell Grouping (4/5)Limitations/dependenciesRU30If more than one LCG covers System Module Rel.2 with activated HSDPA scheduler, BaseBand capacity of each LCG is decreased by 0,25 of subunit which are not seen in the Rel99 CE utilization counters

In WBTS7.0 in case of few LCGs and System Module Rel.2, BTS tries to allocate whole LCG to one System Module. Therefore LCG having more cells will be allocated to System Module with bigger capacity NEWNEW# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential33Local Cell Grouping (5/5)Limitations/dependenciesRU30The operator has a possibility to define Local Cell Groups in two different ways: frequency-layer based (as in previous releases) sector-group based (new way of cell dedication to LCG)

The only one way of Local Cell Groups defining can be selected by the operator.

If sector-group based LCG commissioning was selected, then cells from the same sector can be dedicated to the same Local Cell Group (few sectors can be dedicated to one LCG).

Sector-group based LCG is possible only with pure System Modules rel.2 configuration and two System Modules. With sector-group based LCG commissioning the operator can create up to 2 LCGs (where the first LCG covers capacity of the first System Module while the second LCG covers capacity of the second System Module).

NEW# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential34BaseBand Dimensioning # Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential35HSDPA in RU30# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential36HSDPA schedulerSM Rel.2 HSDPA scheduler (1/2)One HSDPA scheduler supports: Up to 240 HSDPA active users (DC / MIMO / legacy HSDPA users / mixed all HSDPA kind users) From 1 to 6 cells Different LCGs covering baseband capacity of SM with activated HSDPA schedulerHSDPA throughput provided by scheduler depends on: Activated features Number and type of BTS processing sets (# users and throughput) HSDPA throughput commissioning (BB resources allocation)HSDPA schedulers available for HW Rel.1 same as in RU10/RU20 In RU30 there is only one type of HSDPA scheduler with System Module Rel.2Up to 2 HSDPA schedulers are supported with one SM Rel.2# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential37HSDPA schedulerSM Rel.2 HSDPA scheduler (2/2)HSDPA throughput stepsMaximum throughput for HSDPA scheduler00 Mbps1, 2, 3, 4, 5, 642 Mbps7, 8, 9, 10, 11, 1284 Mbps13, 14, 15, 16, 17, 18126 Mbps19, 20, 21, 22, 23, 24168 Mbps25, 26, 27, 28, 29, 30210 Mbps31,32, 33, 34, 35252 MbpsOperator can activate HSDPA scheduler by scheduler throughput steps commissioning.The following HSDPA throughput step values are available: from 0 up to 35 HSDPA throughput commissioning is optional and if not commissioned, BTS will allocate HSDPA throughput based on the default rules (please see next slide) Scheduler not activated Table above does not consider TUP max HSDPA throughput limitationPlease not that minimum allocation rules needs to taken into consideration (please see next slides)# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential38In order to active HSDPA scheduler operator can make HSDPA scheduler. If commissioning was not performed then BTS automatically apply HSDPA baseband allocation according to default rules.

Please note that TUP max HSDPA throughput limitation is not taken into consideration! For the time being (23.09.2010) up to 168Mbps per System Module was communicated.

HSDPA schedulerDefaults rulesHSDPA BaseBand resource allocation before SW update (e.g. RU10, RU20)Allocated throughput for HSPA cells (RU30)Shared scheduler for BB efficiency42 Mbps allocated to every two non-MIMO cells or two MIMO cellsFull BaseBand42 Mbps allocated to every two non-MIMO cells or one MIMO cellMinimum BaseBand Allocation2*42 Mbps allocated to every 1-6 non-MIMO cells or 1-3 MIMO cellsHSDPA 16 Users per cellNot available# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential39HSDPA schedulerMinimum allocation ruleTo assure optimal HSDPA performance BTS checks whether allocated for HSDPA resources are appropriate for BTS configurationIn case when commissioned throughput is too low in reference to number of HSDPA cells, BTS prevents to allocate lower HSDPA throughput below level specified by minimum allocation ruleMIMO cellsMinimum HSDPA throughputNon-MIMO cellsMinimum HSDPA throughput1-342 Mbps1-642 Mbps4-6126 MbpsTable below presents minimum allocation rule for HSDPA scheduler# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialHSDPA schedulerHSDPA baseband requirementsIn RU30 HSDPA scheduler does not consume Rel99 CE licenses but depending on commissioned HSDPA throughput limits number available subunitsTable below presents combined HSDPA throughput for System Module Rel.2 and corresponding HSDPA baseband capacity utilization.Maximum HSDPA throughput for System Module Rel.2 HSDPA baseband capacity reservation(number of subunits)0 MbpsHSDPA schedulers not activated42 Mbps284 Mbps2126 Mbps3168 Mbps3210 Mbps4252 Mbps4294 Mbps5336 Mbps5378 Mbps6420Mbps6462 Mbps7504 Mbps7# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential41HSDPA scheduler HSDPA - Formula to calculate HSDPA Subunit ConsumptionBaseBand capacity (subunits) required by HSDPA can be calculated according to the formula below:Subunits_for_HSDPA = Max { (Round up ((2 * MIMO_cells + non-MIMO_cells) / 6) + 1) ; subunits_for_HSDPA_throughput) + Number_of_LCGs * 0,25

HSDPA TP SubunitsWhere: MIMO_cells = number of HSDPA cells with MIMO activatednon-MIMO_cells = number of HSDPA cells without MIMOSubunits_for_HSDPA_throughput = number of subunits based on commissioning (see below)Number_of_LCGs = number of LCGs covering System Module Rel.2 BB capacity# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential4242HSDPA schedulerHSDPA - Formula to calculate HSDPA Subunit ConsumptionExample: - 3 + 3 + 3 configuration, Rel2 SM & RF Modules, 1 LCG- HSDPA in f1 and f2, MIMO on f1, Rel99 on f3, 84 Mbps HSDPA throughputMIMO_cells = 3 (MIMO is on f1)non-MIMO_cells = 3 (cells in f2 are HSDPA non MIMO cells)Subunits_for_HSDPA_throughput = 2 subunitsNumber_of_LCGs = 1 Local Cell GroupSubunits_for_HSDPA = Max ( (Roundup ((2 * ? + ?) / 6) + 1 ) ; ?) + ? * 0,25= Max (? ; ?) + 0,25 = ? + 0,25 = ?Subunits_for_HSDPA = Max ( (Round up ((2 * MIMO_cells + non-MIMO_cells) / 6) + 1) ; subunits_for_HSDPA_throughput ) + Number_of_LCGs * 0,256 HSDPA cells3 MIMO cellsexample !!!# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential4343HSDPA scheduler HSDPA - Formula to calculate HSDPA Subunit ConsumptionExample: - 3 + 3 + 3 configuration, Rel2 SM & RF Modules, 1 LCG- HSDPA in f1 and f2, MIMO on f1, Rel99 on f3, 84 Mbps HSDPA throughputMIMO_cells = 3 (MIMO is on f1)non-MIMO_cells = 3 (cells in f2 are HSDPA non MIMO cells)Subunits_for_HSDPA_throughput = 2 subunitsNumber_of_LCGs = 1 Local Cell Group3 subunits due to MIMOSubunits_for_HSDPA = Max ( (Roundup ((2 * 3 + 3) / 6) + 1) ; 2) + 1 * 0,25subunits due to HSDPA throughput= Max (3 ; 2) + 0,25 = 3 + 0,25 = 3,25Subunits_for_HSDPA = Max ( (Round up ((2 * MIMO_cells + non-MIMO_cells) / 6) + 1) ; subunits_for_HSDPA_throughput ) + Number_of_LCGs * 0,256 HSDPA cells3 MIMO cellsexample !!!# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential4444HSDPA schedulerSummaryMax. number of Active Users per HSDPA schedulerMax number of cells assign to HSDPA schedulerMax scheduler throughput240(196 DC + MIMO users)6252 MbpsMax number of HSDPA schedulers per System Module Rel.2Max number of HSDPA Active Users per System Module Rel.2Max number of HSDPA cells per System Module Rel.2Max HSDPA peak throughput per System Module Rel.2 /2480 (392 DC + MIMO users)

12 (6 cell per scheduler)504 Mbps (256 Mbps per schedulers)System Module Rel.2 HSDPA scheduler descriptionSystem Module Rel.2 description Tables above do not consider TUP max HSDPA throughput limitation # Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialHSDPA BTS Processing Set resources allocation # Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential46HSDPA BTS Processing Set resources allocationHSDPA BTS processing set specifies: Maximum number of HSDPA users Maximum HSDPA throughputHSDPA processing setMax number of HSDPA users per BTSMax HSDPA throughput per BTSHSDPA BTS processing set 1327,2 MbpsHSDPA BTS processing set 27221 MbpsHSDPA BTS processing set 37284 Mbps# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialHSDPA BTS Processing Set resources allocationAvailable HSDPA BTS processing set resources are distributed among HSDPA schedulers.Different rules are used for active users and throughput distribution.

Total HSDPA licensed throughput is distributed among the available HSDPA schedulers. When the maximum licensed HSDPA throughput per scheduler is calculated, it is divided between HSDPA schedulers proportionally to "Maximum Throughput per HSDPA commissioned values (HSDPA Throughput Step) If there are only HSDPA Processing Set 1 licenses present in BTS, the division of licensed throughput will be done for each scheduler according to the following formula:

Scheduler_licensed_throughput = Round_down { Number_of_HSDPA_Processing_Sets * ( Scheduler_HSDPA_throughput_step / Total_number_of_HSDPA_throughput_step_per_BTS) } * 7,2 Mbps

If there are only HSDPA Processing Set 2 and 3 licenses present in BTS, the division of licensed throughput will be done for each scheduler according to the following formula:

Scheduler_licensed_throughput = Round_down { Number_of_HSDPA_Processing_Sets_ 2 + 4 * Number_of_HSDPA_Processing_Sets_ 3) * ( Scheduler_HSDPA_throughput_step / Total_number_of_HSDPA_throughput_step_per_BTS) } * 21 Mbps

HSDPA throughput:# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialIf after calculations presented above throughput for all schedulers is lower than alllicensed throughput in the BTS, the remaining throughput is distributed with the samegranularity, (7.2Mbps or 21Mbps depending on available HSDPA BTS Processing Sets)prioritizing schedulers in the following order:a) scheduler with licensed throughput below commissioned throughputb) scheduler with lowest licensed throughputc) System Module rel.2 scheduler (FSM1 is prioritized over FSM2)48HSDPA BTS Processing Set resources allocation Total licensed HSDPA users is controlled on BTS level and it can be divided between LCGs according to commissioned shares.

Commissioning share option (HSDPA user share) defines the guaranteed HSDPA user capacity for each LCG. If commissioning is not done then user amount will be equally divided between LCGs.

For example:In case when 1 HSDPA BTS processing set 3 license was bought. It means that available user amount is 72 users. One LCG is created, it means that all amount of user can be taken. In case when 1 HSDPA BTS processing set 3 license was bought and two LCGs were configured. Operator can commission for example 20% of all available users to LCG1 and 40% to LCG2 and this mean that remaining 40% is common for both LCGs and can be shared freely between them.In case when no commissioning is done, whole available amount of users is divided equally per each configured LCG.

HSDPA active users:# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialHSUPA in RU30(System Module Rel.2)# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential50HSUPA resources allocationSystem Module Rel.2 In RU30 HSUPA does not consume Rel99 CE licenses. The maximum baseband resources that can be allocated for HSUPA are described by HSUPA BTS processing sets.

Baseband resources allocated for HSUPA purpose can change dynamically, based on current need (number of active users and combined L1 throughput of all HSUPA users) HSUPA baseband resource allocation is performed on step basis

Up to two HSUPA resource steps can be statistically commissioned for HSUPA

One HSUPA baseband resource is called HSUPA resource step

One HSUPA BTS processing set requires 2 HSUPA resource steps (1/2 subunit)# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialHSUPA resources allocationSystem Module Rel.2 In case when number of available R99 CE licenses and number of HSUPA resources (described by number of available HSUPA BTS processing sets) exceed System Module rel.2 capacity, overlapping baseband capacity can be dynamically exchange between R99 and HSUPA users.

First HSUPA BTS processing set (in each LCG) can be utilized by R99 users (even without R99 CE licenses)

2nd and following processing sets are also dynamic, but they require that corresponding Rel99 CE licenses exists

# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialBaseBand resources allocationOverlapping baseband resourcesRel99 CE licensesHSUPA BTS processing setsHSDPA commissioned throughputSystem Module Rel.2Free (unlicensed) baseband resources not available for R99 users and HSPA data usersNo license overlapping scenarioBaseband resources available for R99 users# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialBaseBand resources allocationOverlapping baseband capacity and static resources reservationRel99 CE licensesHSUPA BTS processing setsBaseband resources available for HSUPA users only!Overlapping baseband capacity can be dynamically share between HSUPA users and R99 user*System Module Rel.2Rel 99 usersHSDPA commissioned throughputHSUPA usersFor overlapping Rel99 CE licenses and licensed HSUPA resources, commissioning can be performed in order to guarantee resources for HSUPA. NOTE: Up to two HSUPA resource steps can be statically commissioned for HSUPAOverlapping scenario* R99 users have always higher priority# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialHSUPA resources allocation (NRT HSUPA users)HSUPA requirements minimum license requirementsTable assumes typical use case when the majority of the users are downlink data dominated and the remaining users are UL data dominated.HSUPA Baseband resources (HSUPA resource steps) dimensioning for NRT HSUPA users should based on the following rule:For example:192 data HSUPA users with combined L1 throughput = 34,8 Mbps- 192 data HSUPA requires:-> 16 HSUPA resource steps are required for HSUPA (4 subunit) / 8 HSUPA BTS processing steps- 34,8 Mbps combined L1 HSUPA throughput requires->12 HSUPA resource steps are required for HSUPA (3 subunit) / 6 HSUPA BTS processing stepsHSUPA required BB resources = max( Users_requirement; Throughput requirements) = max( 16 ; 12) = 16 HSUPA resource steps / 8 HSUPA BTS processing setsBB capacityMax number of HSUPA usersMax HSUPA throughput 2 HSUPA resource steps (1/2 subunit)245,8 Mbps# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialHSUPA resources allocationHSUPA requirements - minimum license requirementsNote: Values are under investigationsTable presents required number of HSUPA resource steps. Maximum throughput and maximum user amount are NOT achieved simultaneously. In case user amount is at maximum then throughput is minimum and vice versa in case when throughput is at maximum then user amount is at minimum (i.e. one user per license allocation). Table assumes typical use case when the majority of the users are downlink data dominated and the remaining users are UL data dominated. Minimum number of data HSUPA UEs per schedulerBaseband minimum decoding capacity[Mbps]2,85,811,617,423,229,034,840,646,452,258,063,869,675,481,287,092,898,6104,4110,2116,000000000000000000000001 - 240,50.511,522.533.544.555.566.577.588.599.51025- 481111,522.533.544.555.566.577.588.599.51049 - 721,51,51,51,522.533.544.555.566.577.588.599.51073 - 96222222.533.544.555.566.577.588.599.51097 - 1202.52.52.52.52.52.533.544.555.566.577.588.599.510121 - 14433333333.544.555.566.577.588.599.510145- 1683.53.53.53.53.53.53.53.544.555.566.577.588.599.510169 - 1924444444444.555.566.577.588.599.510193 - 2164.54.54.54.54.54.54.54.54.54.555.566.577.588.599.510217 - 240555555555555.566.577.588.599.510241 - 2645.55.55.55.55.55.55.55.55.55.55.55.566.577.588.599.510265 - 28866666666666666.577.588.599.510289 - 3126.56.56.56.56.56.56.56.56.56.56.56.56.56.577.588.599.510313 - 3367777777777777777.588.599.510337 - 3607.57.57.57.57.57.57.57.57.57.57.57.57.57.57.57.588.599.510361- 384888888888888888888.599.510385 - 4088.58.58.58.58.58.58.58.58.58.58.58.58.58.58.58.58.58.599.510409 - 43299999999999999999999.510433- 4569.59.59.59.59.59.59.59.59.59.59.59.59.59.59.59.59.59.59.59.510457 - 480101010101010101010101010101010101010101010# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialCS Voice over HSPA # Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential57CS Voice over HSPA Baseband capacity reservation Each CS voice over HSPA user decrease number of HSUPA usersallowed by HSUPA license (HSUPA BTS processing set) and HSDPA license (HSDPA BTS processing set)

However from baseband resources allocation point of view, CS voice over HSPA users require separate baseband resources than NRT HSPA users

Therefore baseband capacity reservation provided by HSUPA BTS processing set(s) and HSDPA processing set(s) is not valid for CS voice over HSPA users# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialCS Voice over HSPABaseband capacity reservation CS voice over HSPA baseband resources are allocated according to traffic demand based on the following priorities:1) Not licensed System Module rel.2 baseband capacity 2) R99 licensed baseband capacity3) HSUPA licensed baseband capacity

One CS voice over HSPA user consumes BB resources by amount corresponding to 1,15 Rel99 CEPlease note that CS voice over HSPA users do not consume Rel99 CE licenses# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialCS Voice over HSPABaseband capacity reservationRel99 CE licensesHSUPA BTS processing stepsBaseband resources available for HSUPA purpose can not be allocated by R99 users (except first HSUPA BTS processing set (2 HSUPA resource steps - >24 Rel99 CE)HSDPA commissioned throughputSystem Module Rel.2Unlicensed baseband resources not available for R99 users and and NRT HSPA users. 1) CS voice over HSPA users allocation unlicensed baseband capacityBaseband resources available for R99 usersPriority 1: CS voice over HSPA users are allocated into unlicensed baseband capacity# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialCS Voice over HSPABaseband capacity reservationRel99 CE licensesHSUPA BTS processing stepsBaseband resources available for NRT HSUPA users can not be allocated by R99 users (except first HSUPA BTS processing set (2 HSUPA resource steps - >24 Rel99 CE)HSDPA commissioned throughputSystem Module Rel.22) CS voice over HSPA users allocation Rel99 CE licensed capacityBaseband resources available for R99 usersIf unlicensed baseband capacity not available (or already occupied) CS voice over HSPA users are allocated into Rel99 licensed baseband capacity# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialCS Voice over HSPABaseband capacity reservationRel99 CE licensesBaseband resources available for NRT HSUPA users can not be allocated by R99 users (except first HSUPA BTS processing set (2 HSUPA resource steps - >24 Rel99 CE)HSDPA commissioned throughputSystem Module Rel.23) CS voice over HSPA users allocation HSUPA licensed capacityBaseband resources available for R99 usersIf unlicensed baseband capacity not available (or already occupied) and Rel99 licensed baseband capacity not available (or already occupied) CS voice over HSPA users are allocated into HSUPA licensed baseband capacityRel 99 usersOverlapping baseband capacity can be dynamically share between HSUPA users and R99 user*HSUPA BTS processing stepsHSUPA users# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialHSUPA BTS Processing Set resources allocation # Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential63HSUPA BTS Processing Set resources allocationHSUPA BTS processing set specifies: Maximum number of HSUPA users Maximum HSUPA throughputHSUPA processing setMax number of HSUPA users per BTSMax HSUPA throughput per BTSHSUPA BTS processing set 1245,8 MbpsPlease note that HSUPA license (HSUPA BTS processing set) does not assure maximum throughput to all users simultaneously but it provides maximum throughput (5,8Mbps) to one user and minimum throughput to all 24 users# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialHSUPA BTS Processing Set resources allocationAvailable HSUPA BTS processing set resources needs to be distributed among HSUPA schedulers If BaseBand pooling is used then BTS will divide HSUPA licenses between LCGs according to commissioned share (HSUPA user/throughput license share). Sum of LCG shares is always 100%. HSUPA licence share is performed with HSUPA BTS processing set licence granularity. If licenses cannot be share equally between LCGs, in that case BTS will divide higher amount of licenses to LCG starting from lowest LCG number. E.g.: if commissioned shares are 50% / 50% and there are 5 HSUPA licenses, then LCG1 gets 3 licenses and LCG2 gets 2 licenses. If HSUPA scheduler is present in both System Modules, in this case BTS will allocate HSUPA licenses proportionally to baseband capacity for traffic use of each system module, with BTS processing set granularity.Please note that every HSUPA user (UL:HSUPA bearer, DL:HSDPA bearer) consumes HSUPA license (HSUPA BTS processing set) and HSDPA license (HSDPA BTS processing set)# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany ConfidentialCommon Control Channels allocation# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential66Common Control ChannelsGeneral informationProcessing of Common Control Channels requires certain amount of Rel99 CE.

In general number of Rel99 CE allocated for CCCH processing depends on:Number of cellsCell rangeNumber of signaturesNumber of Rx branches

DL1 x P-SCH1 x S-SCH1 x P-CCPCH1 x P-CPICH1 x PICH1 x AICH 3 x S-SCCPCHULPRACHCell with radius higher than 20km is called Extended Cell# Nokia Siemens Networks RU30 BaseBand dimensioning rulesCompany Confidential67CCCH allocationCCCH requirementsRel.2 HW System Modules subrack provides processing resources for Common Control Channel for basic configurations: 1 * System Module : 3 cells/20 km (eg. 1+1+1 with 20 km cells) 1 * System Module : 6 cells/10 km (eg. 2+2+2 with 10 km cells) 2 * System Module: 6 cells/20 km (eg. 2+2+2 with 20 km cells) 2 * System Module: 9 cells/10 km (eg. 3+3+3 with 10 km cells) 2 * System Module: 12 cells/10 km (eg. 4+4+4 with 10 km cells)

Other configurations that can be served only with Rel99 CE resources included in Release 2 HW System Modules can be determined with the formula below:

i - # of cells (1-6)Cell range user cell radius referred in km rounded up to next 5km# of signatures max number of preamble signatures 1=< z =