Dimension WCDMA

8/9/2019 Dimension WCDMA

http://slidepdf.com/reader/full/dimension-wcdma 1/72

1 (72))) © Nokia Siemens Networks

Confidential

Issue 01A

WCDMA RAN, Rel.RU30,Operating Documentation

Dimensioning WCDMARAN: Multiradio 10 BTSBaseband

DN09135678Issue 01A Approval date: 2013-05-09

Confidential



Dimensioning WCDMA RAN: Flexi Multiradio 10 BTS Baseband


Confidential

Issue 01A

The information in this document is subject to change without notice and describes only the productdefined in the introduction of this documentation. This documentation is intended for the use of Nokia

Siemens Networks customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be used, reproduced, modified o r transmitted in any form or meanswithout the prior written permission of Nokia Siemens Networks. The documentation has been preparedto be used by professional and properly trained personnel, and the customer assumes full responsibilitywhen using it. Nokia Siemens Networks welcomes customer comments as part of the process ofcontinuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liability arising inconnection with such hardware or software products shall be defined conclusively and finally in aseparate agreement between Nokia Siemens Networks and the customer. However, Nokia SiemensNetworks has made all reasonable efforts to ensure that the instructions contained in the document areadequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessaryby Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENTWILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR

ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL ORCONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT,REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISEFROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and otherintellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of NokiaCorporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, andthey are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2013. All rights reserved.







Confidential

Issue 01A

Summary of changes

This document comprises 72 pages.

Changes between issues 01A (2013-05-09, RU30) and 01 (2013-02-14, RU30)

Updated the following chapters:

- Chapter 2.2.2 HSUPA BTS Processing Set definition update

- Chapter 4.1.2 HSUPA 2ms TTI FDPCH Dimensioning table update

- Chapter 4.1.3 4 way Rx Div feature and PIC pool support update

- Chapter 4.1.6 Formula for amount of HSUPA BTS Processing Set was updated





Confidential

Issue 01A

List of Figures and Tables

Figure 1 Multiradio Flexi BTS WCDMA modules .................................................................................... 7

Figure 2 FSMF System Module structu re ................................................................................................. 8

Figure 3 RU30 System Module Rel.3 BTS ................................................................................................ 8

Figure 4 FSMF System Module, 1 LCG scenario with 12 HSPA (non-MIMO) cells and 1 in terferencecancellation (PIC pool) unit ...................................................................................................... 11

Figure 5 CCCH pool included in System Module Rel.3 (FSMF) capacity .......................................... 17

Figure 6 CCCH processing resources allocation procedure with System Module Rel.3 ................ 21

Figure 7 Examples of sector based commission ing ........................................................................... 24

Figure 8 Sector based pooling possible LCG configurations ............................................................ 24

Figure 9 Example of Rel99 CE allocation .............................................................................................. 27

Figure 10 System Module Rel.3 (1LCG) exemplary Tcell conf igurations ............................................ 30

Figure 11 Example of baseband capacity reservation without l icense overlapping .......................... 38

Figure 12 Example of baseband capacity reservation with license overlapping .............................. 38

Table 1 Number of subunits inside System Module Rel.3 .................................................................... 9

Table 2 System Module Rel.3 LCG configuration type details ........................................................... 10

Table 3 HSDPA schedulers and CCCH requirements (non-MIMO and non-VAM cells) ..................... 12

Table 4 HSDPA schedulers and CCCH requirements (MIMO or VAM non-MIMO cells) .................. 13

Table 5 Minimum HSDPA subunits requirement ................................................................................... 14

Table 6 CCCH Processing Sets and subunits required for CCCH processing with System ModuleRel.3 (2 way Rx Div assumed) and single LCG ...................................................................... 19

Table 7: HSUPA BTS Process ing Set baseband maximal capacity reservation in RU30 (FSMF +FBBA+FBBA assumed) ............................................................................................................ 23

Table 8 Baseband resources required per one Rel99 traffic channel in RU30 (System ModuleRel.3) ........................................................................................................................................... 26

Table 9 LCG configuration types for System Module Rel.3 ................................................................ 28

Table 10 System Module Rel.3 HSDPA scheduler details ................................................................... 29

Table 11 Associated DCH and Rel99 CE usage ................................................................................... 34

Table 12 Flexi System Module Rel.3 HSPA LCG properties ............................................................... 35

Table 13 HSUPA static resources allocation for System Module rel.3 ................................................ 36

Table 14 HSUPA resource step baseband capacity ............................................................................ 37

Table 15 HSUPA resource allocation in number of subunits for System Module Rel.3 (F-DPCH10ms TTI users) ......................................................................................................................... 39

Table 16 HSUPA resource allocation in number of subunits for System Module Rel.3 (non-F-DPCH 10ms TTI users) (tentative values) ............................................................................... 45

Table 17 HSUPA resource allocation in number of subunits for System Module Rel.3 (F-DPCH2ms TTI users) (tentative values) ............................................................................................ 51

Table 18 HSUPA resource allocation in number of subunits for System Module Rel.3 (non-F-DPCH 2ms TTI users) (tentative values) ................................................................................. 57

Table 19 Max number of HSUPA subunits with System Module Rel.3 .............................................. 63

Table 20 PIC pool unit summary information ....................................................................................... 65

Table 21 CS Voice over HSPA users (System Module Rel.3)................................................................ 65





Confidential

Issue 01A

1 Introduction

This dimensioning guideline is focused on Flexi Multiradio 10 BTS WCDMAdimensioning (Flexi System Module Rel.3) in RU30 release covering WBTS7.0release. For detailed information about RU30 BTS dimensioning for SystemModule Rel.1 or System Module Rel.2, see RU30 Flexi BTS BasebandDimensioning guide.





Confidential

Issue 01A

2 Flexi Multiradio 10 BTSWCDMA

Figure 1 Multiradio Flexi BTS WCDMA modules shows the self-supportingBTS modules comprising the Multiradio Flexi 10 BTS WCDMA:

Radio Module provides the Radio Frequency (RF) function. A maximumof three RF Modules can be directly connected to the Master SystemModule.

System Module provides baseband processing as well as control andtransmission function

System Module capacity depends on system module type, for details, seeChapter 2.1.1. The number of activated Rel99 CEs or HSPA ProcessingSets can be increased by license control.

Figure 1 Multiradio Flexi BTS WCDMA modules

2.1 Flexi Multiradio 10 BTS WCDMA capacity

There are five kinds of RF Modules available:

Release1 Single RF Module (50W–supporting one sector)

Release1 Dual RF Module ( 50W–supporting one or two sectors)

Release2 Triple RF Module (70W–supporting one, two, or three sectors)

Release2 RRH Module (70W–supporting one sector)

Release3 Triple RF Module (90W/6Gb OBSAI interface–supporting one,two or three sectors)

Flexi Multiradio 10 BTS provides up to 12-cell capacity. Up to six sectors or upto eight carriers per configuration are supported by the hardware. The output





Confidential

Issue 01A

power options of min 8/10/15/20/30/40W/60W or 80W (depending on the RFmodule) are available.

For more specific information related to supported configurations, see CablingFlexi WCDMA BTS and Creating Configurations, Commissioning Flexi WCDMABTS, and Flexi Multiradio BTS WCDMA Supported and Planned Configurationsdocuments.

System Module Rel.3 (the so called Flexi Multiradio 10 BTS System Module) isnew software, defined BTS for four different technologies (GSM/WCDMA/LTEand LTE-Advanced). Capacity of System Module Rel.3 (FSMF) can be extendedwith optional capacity extension submodules (FBBA). Up to two capacitiesextension submodules can be used with single System Modules Rel.3. FSMFSystem Module and FBBA extension submodules are seen as one common poolof baseband capacity. For more specific information about System ModuleRel.3, see RAN2262: Flexi Multiradio System Modules feature description.

Figure 2 FSMF System Module structure shows the Flexi Rel.3 MultiradioSystem Module FSMF. It has 5.5 subunits.

Figure 2 FSMF System Module structu re

In RU30, Multiradio 10 BTS consists of single System Module Rel.3 only andcan be used with RF HW Rel.2 or newer. A maximum of 12 cells (2-way Rx Div)

per BTS are supported. Figure 3 RU30 System Module Rel.3 BTS shows asample of the master System Module Rel.3.

Figure 3 RU30 System Module Rel.3 BTS

2.1.1 Flexi Multiradio 10 BTS system module capacity

The System Module Rel.3 baseband consists of subunits that can be used for:

CCCH processing

R99 users processing

HSDPA users, and throughput processing

HSUPA users and throughput processing

CS Voice over HSPA users processing

Interference cancellation processing







Confidential

Issue 01A

Table 2 Table 2 System Module Rel.3 LCG configuration type details enlists the LCG configuration type details related to the number of supportedHSPA cells/HSDPA schedulers amount.

LCGconfigurationtype

Max numberof supportedcells

Max numberof HSPAcells

Number ofHSDPAschedulers

Rel.99 only 12 0 0

small HSPA 6 6 1

normal HSPA 12 12 2

Table 2 System Module Rel.3 LCG configuration type details

With small HSPA and normal HSPA configuration, HSDPA scheduler resources(HSDPA subunits) provide certain amount of CCCH baseband processingresources (so called CCCH pools) that can be used as additional CCCHprocessing resources. For more information, see Chapter 2.2.1.

The amount of LCG subunits for pure traffic can be calculated by subtractingfrom LCG baseband capacity:

CCCH processing subunits (if needed to be licensed from SM Rel.3capacity)

HSDPA scheduler processing subunits

Interference Cancellation units (PIC pools) subunits

HSUPA static allocation processing subunits

Figure 4 FSMF System Module, 1 LCG scenario with 12 HSPA (non-MIMO)cells and 1 interference cancellation (PIC pool) unit shows how the subunitsfor pure traffic capacity can be used for R99 (DCH) users, HSDPA users (A-DCH/SRB), and HSUPA users (HSUPA scheduler).







Confidential

Issue 01A

- Two CCCH Processing Set licenses requi red

* - Baseband capacity available for additional CCCH processing included inHSDPA scheduler resources (CCCH Processing Set(s) required for activation)

Table 3 HSDPA schedulers and CCCH requirements (non-MIMO and non-VAM cells)

Table 4 HSDPA schedulers and CCCH requirements (MIMO or VAM non-MIMO cells) lists the HSDPA schedulers and CCCH processing requirementsfor typical scenarios.

Note that this assumes MIMO cells, 10km cell range, and 2-way Rx Diversity. Amaximum of 12 cells per BTS are supported.

LCGconfiguration

Number ofHSPA (VAM

MIMO or VAMnon-MIMO)

cells per LCG

1st

LCG[subunits]

2nd

and nextLCG [subunits]

Rel99 only 0 (6 non-HSPAcells)

0 0,5 (CCCH)

Rel99 only 0 (12 non-HSPAcells)

0,5 (CCCH) 1 (CCCH)

Small Up to 4 cells 0,625 (HSDPAscheduler*)

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

scheduler*) = 1,125

Small 5 - 6 cells 1,125 (HSDPA

scheduler*)

0,5 (CCCH) +1,125 (HSDPA

scheduler*)

= 1,625

Normal Up to 6 cells 1,125 (HSDPAscheduler*)

0,5 (CCCH) +1,125 (HSDPA

scheduler*) = 1,625

Normal 7 – 8 cells 1,625 (HSDPAscheduler*)

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

scheduler*) = 2,125

Normal 9 - 10 cells 2,125 (HSDPAscheduler*)

0,5 (CCCH) +

2,125 (HSDPAscheduler*) = 2,625

Normal 10 - 12 cells 2,625 (HSDPAscheduler*)

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

scheduler*) = 3,125

- One CCCH Processing Set license required

- Two CCCH Processing Set licenses required

* - Baseband capacity available for additional CCCH processing included inHSDPA scheduler resources (CCCH Processing Set(s) required for activation)





Confidential

Issue 01A

Table 4 HSDPA schedulers and CCCH requirements (MIMO or VAM non-MIMO cells)

All values in the tables above were calculated according to Equation 1 LCGconfiguration subunits requirement (Small HSPA or Normal HSPA

configuration . Equation 1Equation 2 LCG cells factor and Equation 3Number of LCG available CCCH processing resources are explained below.

Baseband consumption for other configurations can be calculated usingformulas presented below.

Equation 1:

HSDPA_subunits=max{(Cells_factor/2)–0,5;Min_HSDPA_subunits}+0,125

Equation 1 LCG configuration subunits requirement (Small HSPA orNormal HSPA conf iguration

where:

HSDPA_subunits refers to the baseband resources responsible for HSDPAscheduler(s). In addition to HSDPA baseband resources, HSDPA subunits offercertain amount of CCCH baseband processing resources. For more information,see Chapter 2.2.1.

Cells_factor refers to the factor calculated according to

Equation 2 LCG cells factor

Min_HSDPA_subunits refers to the minimum number of LCG configurationsubunits requirements from

Table 5

Equation 2:

Cells_factor=Roundup {(Roundup(non_MIMO_cells/3)+MIMO_cells)/2}

Equation 2 LCG cells factor

where:

non_MIMO_cellsrefer to the number of non-MIMO and non-VAM cells inLCG (sum of Rel.99 only and HSPA cells)

MIMO_cellsrefer to the number of HSPA MIMO or non-MIMO but VAM

cells in LCG.

Table 5 Minimum HSDPA subunits requirement lists the minimum number ofLCG configuration subunits requirements used in Equation 1 LCGconfiguration subunits requirement (Small HSPA or Normal HSPAconfiguration .

LCGconfiguration

type

Minimum number of HSDPAsubunits (Min_HSDPA_subunits)

small HSPA 0.5





Confidential

Issue 01A

LCGconfiguration

type

Minimum number of HSDPAsubunits (Min_HSDPA_subunits)

normal HSPA 1

Table 5 Minimum HSDPA subunits requirement

Examples:

1) Scenario assumptions:

FSMF/5.5 subunits (1 LCG-normal HSPA configuration)

12 cells/10km/2-way Rx Div (6 MIMO and 6 non-MIMO cells (3Rel.99 only cells + 3 HSPA non-MIMO cells))

10km cell range/2-way Rx Div VAM is not used

interference cancellation for 6 cells (1 PIC pool required)

Cells_factor=Roundup{(Roundup(non_MIMO_cells/3)+MIMO_cells)/2}

= Roundup{(Roundup(6/3)+6)/2}

= Roundup{(Roundup(2)+6)/2}

= Roundup{(2+6)/2}

= Roundup{8/2}

= Roundup{4}

= 4

HSDPA_scheduler_subunits=max{Cells_factor/2–0.5;Min_HSDPA_scheduler_subunits}+0,125

= max{4/2-0.5;1}+0.125

= max{1.5;1}+0.125

= 1.5+0.125

= 1.625

Note that since only one LCG is available, the whole System Module Rel.3baseband capacity (5.5 subunits) is available (dedicated) for that LCG.

LCG_pure_traffic_subunits =LCG_dedicated_subunits– Additional_CCCH_subunits–PIC_pool_subunits–HSDPA_subunits

= 5.5–0–1–1.625

= 2.875





Confidential

Issue 01A

Note that CCCH processing for 6cells/10km/2-way Rx Div are covered byresources included in SM Rel.3 capacity. The remaining 6 cells/10km/2-way RxDiv are processed with resources included in HSDPA scheduler subunitscapacity (1xCCCH Processing Set licenses needed).

Therefore, the LCG pure traffic capacity is 2.875 subunits .

2) Scenario assumptions:

FSMF+FBBA/11.5 subunits (2LCGs: 1st LCG/12 cells-normal

HSPA configuration; 2nd

LCG/6 cells–small HSPA configuration)

1st LCG: 12 cells/10km/2-way Rx Div (12 non-MIMO cells(12

HSPA cells))/8.5 subunits dedicated

2nd

LCG: 6 cells (6 non-MIMO cells (3 Rel.99 only+3 HSPAcells))/3 subunits dedicated

10km cell range/2-way Rx Div VAM is not used

interference cancellation for 12 cells/LCG1 (2 PIC poolsconfigured)

LCG1 pure traffic capacity calculation:


= Roundup{(Roundup(12/3)+0)/2}

= Roundup{(Roundup(4)+0)/2}

= Roundup{(4+0)/2}

= Roundup{4/2}

= Roundup{2}

= 2

HSDPA_subunits=max{Cells_factor/2–0.5;Min_HSDPA_subunits}+0,125

= max{2/2–0.5;1}+0.125

= max{0.5;1}+0.125

= 1+0.125

= 1.125

Note that CCCH processing for 6cells/10km/2-way Rx Div are covered byresources included in SM Rel.3 capacity. The remaining 6 cells/10km/2-way RxDiv are processed with resources included in HSDPA scheduler subunitscapacity (1x CCCH Processing Set licenses needed).





Confidential

Issue 01A

According to scenario assumptions during BTS commissioning, 8.5 subunitswere dedicated to LCG1.

LCG_pure_traffic_subunits=LCG_dedicated_subunits– Additional_CCCH_subunits–PIC_pool_subunits–HSDPA_subunits

= 8.5–0–2–1.125

= 5.375

Therefore, the LCG1 pure traffic capacity is 5.375 subunits.

LCG2 pure traffic capacity calculation:


= Roundup{(Roundup(6/3)+0)/2}= Roundup{(Roundup(2)+0)/2}

= Roundup{(2+0)/2}

= Roundup{4/2}

= Roundup{1}

= 1

HSDPA_subunits=max{Cells_factor/2–0.5;Min_HSDPA_subunits}+0.125

= max{1/2–0.5;0.5}+0.125

= max{0;0.5}+0.125

= 0.625

LCG 2 requires one CCCH pool (0.5 subunit) for CCCH processing (1xCCCHProcessing Set license required). Note that any additional CCCH processing (forexample, in extended cell range case) can be done with baseband resourcesincluded in HSDPA scheduler subunits capacity (CCCH Processing Set licenserequired)

According to scenario assumptions during BTS commissioning, 3 subunits werededicated to LCG 2.

LCG_pure_traffic_subunits=LCG_dedicated_subunits–CCCH_subunits–PIC_pool_subunits–HSDPA_subunits

= 3–0.5–0–0.625

= 1.875

Therefore, the LCG2 pure traffic capacity is 1.875.





Confidential

Issue 01A

2.2. Common Control Channels

The following DL Common Control Channels are supported in each cell in BTS:

1xP-SCH (Primary–Synchronization Channel)

1xS-SCH (Secondary–Synchronization Channel) 1xP-CCPCH (Primary–Common Control Physical Channel)

1xP-CPICH (Primary–Common Pilot Channel)

1xPICH (Paging Indicator Channel)

1xAICH (Acquisition Indicator Channel)

3xS-SCCPCH (Secondary Common Control Physical Channel)

In the UL, the resources for processing the PRACH channel per each cell arerequired.

The cells with ranges bigger than 20km are called extended cells. Requiredbaseband resources for Common Control Channels for extended cells aredescribed separately in Chapter 5.

Baseband resources allocated for CCCH are LCG specific. It means that everyLCG needs to have own CCCH processing resources for all cells dedicated toLCG according to cell radius, Rx Div type and number of cells dedicated to LCG.

CCCH baseband processing resources are statically allocated in steps, so calledCCCH pools. Each CCCH pool (except CCCH pool included in System Modulecapacity) requires CCCH license - CCCH Processing Set license – for activation.

2.2.1 CCCH requirements for Multi radio 10 BTS systemmodules

Similar to Rel.2 HW, System Module Rel.3 (FSMF) provides one CCCH poolincluded in FSMF Core Module capacity which does not require any license.

Figure 5 CCCH pool included in System Module Rel.3 (FSMF) capacity

Below you can find a list of typical configurations covered by single CCCH poolincluded in System Modules Rel.3 capacity.

1 * System Module: 3 cells/20 km (for example 1+1+1 with 20 km cells);

1 * System Module: 6 cells/10 km (for example 2+2+2 with 10 km cells);

Listed above configuration assumes 2-way Rx Div enabled. If 4-way Rx Divfeature is enabled then number of cells or cell range is halved.





Confidential

Issue 01A

In case when more cells or higher cell radius is needed additional basebandresources (CCCH pools) and CCCH Processing Set licenses need to beallocated for CCCH processing. One System Module Rel.3 CCCH poolcorresponds to 0.5 subunit.

Number of cells that can be served with single CCCH pool from System ModuleRel.3 can be determined with the formula below:

cellsof

i

_ _ #

1

ii 480Rx)*Signaturesof #*Range(Cell

where:

i – number of cells (from one to six);

Cell range – user cell radius referred to in kilometers (rounded up to thewhole kilometer that is divisible by five);

# of Signatures - means maximum number of Preamble signatures 1=<z =< 4.

where:

2-way Rx div:

0km< r <=60km # of signatures = 4;


120km<r<180km # of signatures = 1.

4-way Rx div:




Rx – {2 ; 4} if 4 way Rx diversity Rx= 4, otherwise Rx =2

For example:

1) FSMF, 1 LCG - R99 only configuration, 12 cells/10km cell range, 2way Rx Div.

- 2 CCCH pools needed to cover 12 cells/10km:- 0 x CCCH Processing Set (CCCH pool included in System

Module capacity) required for 6 cells/10km- 1 x CCCH Processing Set required for 6 cells/10km

2) FSMF + FBBA, 1 LCG - R99 only configuration, 12 cells/20km cellrange, 2 way Rx Div.

- 0 x CCCH Processing Set (CCCH pool included in System Modulecapacity) required for 6 cells- 1 x CCCH Processing Set required for 6 cells





Confidential

Issue 01A

NOTE:

With System Module Rel.3 single cell cannot be split between two

CCCH pools.

The HSDPA scheduler(s) resources (HSDPA subunits) provide certain amountof baseband resources (CCCH pools) that can be used for additional CCCHprocessing. It means that each LCG requires at least one CCCH pool (0.5subunit) for CCCH processing unless CCCH processing is performed withresources included in SM Rel.3 baseband capacity. CCCH processing forremaining cells can be performed with baseband resources included in HSDPAscheduler capacity (HSDPA subunits). To use these resources for CCCHprocessing CCCH Processing Set licenses are required.

Below you can find a list of exemplary configurations and CCCH Processing Setlicenses / CCCH subunits requirements for different LCG configuration types.

LCG

configurationtype

3cells/20km 6cells/10km 6cells/20km 9cells/10km 9cells/20km 12cells/10km 12cells/20km

R99 Only

0 CCCHProcessing

Sets /0subunit

0 CCCHProcessing

Sets /0subunit

1 CCCHProcessingSets /0.5subunit


2 CCCHProcessing

Sets /1subunit



Small HSPA

0 CCCHProcessing

Sets /0subunit

0 CCCHProcessing

Sets /0subunit

1 CCCHProcessing

Set /0subunit

- - - -

Normal HSPA

(non-MIMOcells*

assumed)

0 CCCH

ProcessingSets /0subunit

0 CCCH


1 CCCH


1 CCCH

ProcessingSet /0

subunit

2 CCCH


1 CCCHProcessing

Set /0 subunit

3 CCCH

ProcessingSets /0.5subunit

Normal HSPA(MIMO cells**

assumed)

0 CCCHProcessing

Sets /0subunit

0 CCCHProcessing

Sets /0subunit

1 CCCHProcessing

Sets /0subunit

1 CCCHProcessing

Set /0subunit

2 CCCHProcessing

Set /0subunit

1 CCCHProcessing

Set /0 subunit

3 CCCHProcessing

Set /0 subunit

*non-MIMO and non-VAM cells assumed

** MIMO or VAM non-MIMO cells assumed

Table 6 CCCH Processing Sets and subunits required for CCCHprocessing with System Module Rel.3 (2 way Rx Div assumed) and singleLCG

The amount of CCCH pools included in HSDPA scheduler(s) basebandresources can be determined with the formula below:

Equation 3:

Number_of_additional_CCCH_pools=

max{Min_HSDPA_subunits;(Cells_factor/2)–0.5} *2





Confidential

Issue 01A

Equation 3 Number of LCG available CCCH processing resources

where:

Min_HSDPA_subunits - Minimum number of HSDPA subunits from

Table 5

For example:

FSMF / 5.5 subunits (1 LCG - Normal HSPA configuration);

12 cells/10km/2way Rx Div (6 MIMO and 6 non-MIMO cells (3 Rel.99only cells + 3 HSPA non-MIMO and non-VAM cells));

Cells_factor = Roundup{ (Roundup (non_MIMO_cells/3) + MIMO_cells ) /2 } = Roundup{ (Roundup(6/3) + 6) / 2} = Roundup{ (Roundup(2) + 6 ) / 2} = Roundup{ (2 + 6) /2} = Roundup{ 8/2 } = Roundup{ 4 } = 4

Number_of_additional_CCCH_pools = max { Min_HSDPA_subunits ;(Cells_factor / 2) – 0.5 } * 2 = max { 1 ; ( 4 / 2) – 0.5 } * 2 = max { 1 ; 2 –0.5 } * 2 = max { 1 ; 1.5} * 2 = 1.5 * 2 = 3

Three additional CCCH Pools are available in HSDPA schedulerresources (HSDPA subunits). To use these resources for CCCHprocessing (as additional CCCH processing resource), CCCH ProcessingSet licenses are required.





Confidential

Issue 01A

Figure 6 CCCH processing resources allocation procedure with SystemModule Rel.3

CCCH pools included in HSDPA scheduler(s) baseband resources can be usedfor additional CCCH processing (if needed, for example, extended cell rangecase or higher cells configuration). CCCH Processing Set license is needed foractivation.

2.2.2 Capacity licenses

The Flexi WCDMA BTS licensed capacity defines the capacity that the operatorhas purchased. The licensed capacity can be less than the maximum hardware

capacity.

Flexi WCDMA BTS Baseband capacities are allocated according to the capacitylicense file. Because the sites exist in high volumes in the network, NokiaSiemens Networks does not generate licenses for these network elementsdirectly (NE licenses), but so-called pool licenses are used. This means that theuser gets the license to use a dedicated amount of features or capacity (poollicense) and it is up to the user to determine how these NE licenses aredistributed towards the network elements.

As an example, the operator buys a pool license for 10 000 Rel99 CE for BTSs.The operator gets a pool license file that allows use of this capacity. With thispool license and the help of the license management tools in NetAct, one candistribute the capacity according to the capacity needs. For example: 120 Rel99





Confidential

Issue 01A

CE for BTS-1, 70 Rel99 CE for BTS-2, and so on. For this purpose, NetActgenerates the appropriate license files and downloads them to the networkelements.

There are four types of capacity licenses (System Module Rel.3):

CCCH Processing Set license- Applicable only for CCCH processing (might be required for high

cell configurations or extended cell range case)

Rel99 CE license- Applicable for Rel99 traffic

HSDPA BTS Processing Set license- Applicable for HSDPA throughput and HSDPA users

HSUPA BTS Processing Set license- Applicable for HSUPA throughput and HSDPA users

The HSDPA BTS processing set describes the maximum HSDPA capability thatallows reaching a certain number of HSDPA users and DL throughput.

Note that the HSDPA BTS processing set does not directly increase the capacityfor maximum user amount and throughput. Separate ASW (applicationsoftware) licenses for peak throughput and user amount are required.

HSDPA BTS processing set capacities are as stated below:

HSDPA BTS processing set 1: 32 users and 7.2Mbps;

HSDPA BTS processing set 2: 72 users and 21Mbps;

HSDPA BTS processing set 3: 72 users and 84Mbps.

Multi RAB UE having more than one HSDPA RAB is counted as one user fromHSDPA Processing Set license point of view. For example 32 Multi RAB UEs,each having two HSDPA RABs, consume one HSDPA Processing Set 1 licensecapacity.

The HSUPA BTS processing set is an HSUPA capacity reservation insideSystem Module Rel.3 that allows allocation of a certain number of HSUPA usersand UL throughput. The HSUPA scheduler throughput allowed with one HSUPABTS processing set is equal to 5.8Mbps, while the number of users is up to 24.Multi RAB UE having more than one HSUPA RAB is counted as one user fromHSUPA Processing Set license point of view. For example 24 Multi RAB UEs,

each having two HSUPA RABs, consumes one HSUPA Processing Set license.In RU30, HSUPA BTS processing set allows to reach up to 5.8Mbps per HSUPAscheduler, with the minimum number of users or twenty four HSUPA users withthe minimum throughput. The baseband reservation provided by one HSUPABTS processing set is equal to 0,75 subunit maximally, as specified in the tablebelow. HSUPA resource reservation is dynamic and depends on actual totalHSUPA throughput and actual total number of HSUPA users in HSUPAscheduler.





Confidential

Issue 01A

Number ofavailableHSUPABTSProcessingSets

1 2 3 4 5 6 7 8 9 10 11 … 21 22 23 … 99

MaximumusedHSUPAsubunits

0.75 1 1.75 2,5 3.25 4 4,75 5.5 6.25 7 7.75 … 15.75 16.5 16.875 … 16,875

Table 7: HSUPA BTS Processing Set baseband maximal capacityreservation in RU30 (FSMF + FBBA+FBBA assumed)

Number of required Rel99 CE licenses for DCH and A-DCH traffic is calculated

according to formula:#Rel99CE = Max {UL_Rel99CE; DL_Rel99CE}

Equation 4 Number of required Rel99 CE licenses

where:

#Rel99CE – total number of required Rel99 CE licenses;

UL_Rel99CE – total number of required Rel99 CEs in UL channels;

DL_Rel99CE – total number of required Rel99 CEs in DL channels;

For commissioning purposes, all licenses (including Rel99 CE licenses) areactivated for a 14-day period.

For more specific information, see Licenses Management in WCDMA RAN.

NOTE:

License files available at BTS are limited with commissioned licenses.For example if 1000 R99CE license file is available at BTS, whilecommissioned number Of R99Channel El ement s is set to 900, then

BTS shall only use 900 R99 CE licenses.

2.2.3 Local Cell Grouping for Flexi BTS

Local Cell Grouping might be needed if BTS sites with many cells, and can beused in Multi Operator RAN (MORAN) cases to divide baseband capacity toLocal Cell Groups (LCGs). It is possible to use MORAN without Local CellGrouping and dedicated baseband allocation.

A single LCG covers up to twelve cells. However, when 4-way Rx diversity isused, up to six 4-way RX diversity cells can be dedicated to one LCG.





Confidential

Issue 01A

With Local Cell Grouping it is also possible to allocate baseband capacity forLCGs if the same site is divided between several operators (MORAN) who wantto reserve some dedicated BB capacity for own use.

NOTE:

Small HSPA configuration (System Module Rel.3) supports up to 6 cellsin single LCG. If more cells in one LCG need to be supported, NormalHSPA configuration (up to 12 HSPA + R99 cells) or R99 Onlyconfiguration (up to 12 R99 cells) should be configured.

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

Frequency layer based;

Sector based.

Each LCG covers a certain baseband capacity, which is used to serve CCCHand traffic from dedicated cells.

Sector based commissioning

Sector based commissioning allows the following:

Dedication of cells from the same frequency layer(s) to different LCGs ;

Dedication of cells from the same frequency layer(s) to the same LCG.In this case sector based commissioning might give the same results, asfrequency-layer based commissioning.

Figure 7 Examples of sector based commissioning

Sector based pooling allows up to 2 LCGs can be created within single SystemModule Rel.3 (flexible BB pooling)

Figure 8 Sector based pooling possible LCG configurations

FSM rel.3 FSM rel.3

FSM rel.3 (up to 2 LCGs wi th sector based polling)







Confidential

Issue 01A

The number of Rel99 CE depends on RB type and minimum SF. Table 11 and12 present required number of Rel99 CE per each active connection for basicset of RABs.

RAB Traffic classCS/PS

Max Rates

for eachRAB, kbps

Min SFRequired

Rel99 CE per

connection

UL DL UL DL

AMR Speech Conversational CS 1.2 64 128 1 1







Packet Interactive/Background PS 16 64 128 1 1






UDI Conversational CS 64 16 32 4 4

Streaming Streaming CS 57.6 16 32 4 4

Streaming Streaming CS 14.4 64 128 1 1

Table 8 Baseband resources required per one Rel99 traffic channel inRU30 (System Module Rel.3)

2.3.1 Asymmetric UL/DL Rel99 CE allocation

Asymmetric UL/DL allocation means that the UL and DL directions have differentbit rate requirements. The rule for allocating Submodule resources forasymmetric bit rates is based on a higher data rate requirement, but Rel99 CEreservations are done separately for UL/DL. For example, if the UL bearer is 64kbps and the DL bearer 384 kbps, the CE reservation is 4 CE in UL and 8CE inDL.





Confidential

Issue 01A

UL and DL resources have to be allocated inside one subunit but there is nodirect connection between UL and DL resource allocation. In other words, ULand DL resources do not have to be allocated symmetrically across subunit ULand DL capacity (see Figure 12).

Figure 9 Example of Rel99 CE allocation





Confidential

Issue 01A

3 HSDPA and BTS dimensioningSome supported capacities mentioned in this document might require separatelicenses in the RAN before they can be activated. For more information, seeLicenses Management in WCDMA RAN.

For more specific information related to HSDPA, see HSDPA in BTS document

3.1 Flexi System Module Rel.3 HSDPAscheduler

There is one type of HSDPA scheduler available with System Module Rel.3.

The HSDPA scheduler based on System Module Rel.3 supports 64QAM, MIMO,and DC-HSDPA features and supports up to six cells.

The number of HSDPA schedulers is defined per LCG via LCG configurationtype commissioning parameter. With Small HSDPA configuration one HSDPAscheduler is available while Normal HSPA configuration supports 2 HSDPAschedulers.

HSPA ConfigurationNumber of HSDPA

schedulers Max number of

supported HSPA cells

Rel99 Only 0 0 Small HSPA 1 6

Normal HSPA 2 12

Table 9 LCG configuration t ypes for System Module Rel.3

HSDPA scheduler based on System Module Rel.3 is LCG specific – it supportsonly cells dedicated to LCG. In comparison to System Module Rel.2, it does notrequire any additional baseband resources to reach high HSDPA throughput. Inother words, it provides HSDPA throughput up to 252Mbps withoutcommissioning any additional baseband resources for scheduler purpose.

The scheduler provides HSDPA throughput, which depends on activatedfeatures, number and type of BTS processing sets, and HSDPA throughputcommissioning by the operator.

The operator can specify the maximum throughput per each HSDPA scheduler.The maximum throughput for the scheduler is commissioned in steps calledHSDPA throughput steps (HSDPA Throughput Step). For each scheduler,





Confidential

Issue 01A

the operator can select HSDPA throughput step values from 1 up to 35. TheHSDPA throughput step has no impact on HSDPA baseband capacity allocationbut it is used for HSDPA licensed throughput distribution among availableschedulers (for more information, see chapter 3.3). In addition it can be used tolimit HSDPA scheduler throughput. Each HSDPA throughput step correspondsto 7.2Mbps

For example:

Normal HSPA configuration (2 HSDPA schedulers)

Commissioned HSDPA throughput step to scheduler #1 is equal to 2;Commissioned HSDPA throughput step to scheduler #2 is equal to 6;

HSDPA_scheduler #1_throughput = 2 * 7.2Mbps = 14.4Mbps;

HSDPA_scheduler #2_throughput = 6 * 7.2Mbps = 43.2Mbps.

The table below presents the capability of single HSDPA scheduler.

Max. number ofactive users per

HSDPAscheduler

Max. numberof activeusers per

cell

Max number ofcells assign to

HSDPAscheduler

Maxscheduler

throughput

240 128 6 252 Mbps

Table 10 System Module Rel.3 HSDPA scheduler details

HS-Cell_FACH DL user is treated as normal HSDPA user with respect tomaximum number of users supported by HSDPA schedulers.

3.2 Tcell grouping with System Module Rel.3

Tcell grouping is used to group cells to the scheduler based on System ModuleRel.3. Tcell groups 1 and 3 are handled by the first scheduler and Tcell groups 2and 4 are handled by the second scheduler.

One scheduler can handle up to two Tcell groups. If there is only one Tcellgroup used, scheduler can support six cells. If there are two Tcell groups andone scheduler, up to three cells per Tcell group can be supported (up to six cellsare supported totally).

The same Tcell values can be used by different cells if those are allocated todifferent frequency layers. With Dual Cell (DC) HSDPA feature cells from onesector should have the same Tcell value. Note that DC cells from the samesector need to be served by one scheduler, and belong to the same LCG. Notethat both DC cells from the dual cell sector need to be allocated on adjacentfrequencies in one band.

The principles of grouping (maximum four Tcell groups per LCG are possible)are as follows:





Confidential

Issue 01A

Group 1: Tcell values 0, 1 and 2; Group 2: Tcell values 3, 4 and 5; Group 3: Tcell values 6, 7 and 8; Group 4: Tcell value 9.

With Small HSPA configuration (System Module Rel.3), only one HSDPAscheduler (scheduler #1) is available and cells can be grouped with Tcell valuesfrom group 1 and group 3.

Figure 10 System Module Rel.3 (1LCG) exemplary Tcell conf igurations

3.3 HSDPA BTS Processing Set resourcesallocation

HSDPA schedulers based on System Module Rel.3 require HSDPA license socalled HSDPA BTS processing set. To learn more about HSDPA BTSprocessing sets, see chapter 2.2.2.

HSDPA license resources (specified by HSDPA BTS processing sets) aredistributed among HSDPA schedulers/LCGs according to the rules presentedbelow.

1) HSDPA throughput :

Total HSDPA licensed throughput is distributed among the available HSDPAschedulers.

When the maximum licensed HSDPA throughput per scheduler is calculated, itis divided between HSDPA schedulers proportionally to "Maximum Throughputper HSDPA” commissioned values (HSDPA Throughput Step). ”Maximum





Confidential

Issue 01A

Throughput per HSDPA scheduler" is commissioned for each HSDPA schedulerseparately. The commissioned step is 7.2Mbps.

If there are only HSDPA Processing Set 1 licenses present in BTS, thedivision of the 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

Equation 5 Scheduler licensed throughput with BTS Processing Set 1 type only

If there are only HSDPA Processing Set 2 and three licenses are present inBTS, the division of licensed throughput will be done for each scheduler

according to the formula below:Scheduler_licensed_throughput=Round_down{(Number_of_HSDPA_Pr ocessing_Sets_2+4*Number_of_HSDPA_Processing_Sets_3)*(Scheduler_HSDPA_throughput_step/Total_number_of_HSDPA_throughput_step_per_BTS)}*21 Mbps

Equation 6 Scheduler licensed throughput with BTS Processing Set 2 or Set3type

where:

Scheduler_licensed_throughput refers to thelicensed throughputavailable for given scheduler

Number_of_HSDPA_Processing_Sets_2 refers to the number of HSDPAProcessing Sets 2 present in BTS;

Number_of_HSDPA_Processing_Sets_3 refers to the number ofHSDPA Processing Sets 3 present in BTS;

Scheduler_HSDPA_throughput_steprefers to the HSDPA throughputstep commissioned for given scheduler (see chapter 3.1);

Total_number_of_HSDPA_throughput_step_per_BTSrefers to the sumof all commissioned HSDPA throughput steps in the BTS.

If after calculations presented above throughput for all schedulers is lower thantotal licensed throughput in the BTS, the remaining throughput is distributedbetween activated schedulers. Schedulers are prioritized in the following order:

a) Scheduler with lowest value of licensed throughput divided bycommissioned throughput;

b) Schedulers belonging to LCG with the lowest ID (for Normal HSPAconfiguration (2 HSDPA schedulers activated) scheduler#1 isprioritized over scheduler#2)

Distribution of remaining throughput is done iteratively with resolution 7.2Mbpsor 21Mbps depending on available HSDPA Processing Set.





Confidential

Issue 01A

If there are no HSDPA BTS Processing Sets licenses available, BTS sets 0Mbps as throughput to all schedulers.

For example:

BTS configuration with two HSDPA schedulers (for example,NormalHSPA configuration) and four HSDPA Processing Sets:

- 3x HSDPA Processing Set 2 (3x 21Mbps) and 1x HSDPAProcessing Set 3 (1x 84Mbps) licenses available. Total licensedthroughput is 147Mbps

BTS has two HSDPA schedulers activated with following commissionedthroughput:

- Scheduler_#1 HSDPA Throughput Step=6 (42Mbps)

- Scheduler #2 HSDPA Throughput Step=18 (126Mbps)

According to Equation 6 scheduler licensed throughput is calculated as follows:Scheduler #1 = Round_down { (3 + 4* 1) * (6 / (6+18)) } * 21 Mbps =21Mbps

Scheduler #2 = Round_down { (3 + 4* 1) * (18 / (6+18)) } * 21 Mbps =105Mbps

Total licensed throughput available with HSDPA Processing Sets is147Mbps, while total scheduler licensed throughput is 21Mbps +105Mbps = 126Mbps, thus remaining 21Mbps is distributed toschedulers according to priority:

a) Scheduler with lowest value of licensed throughput divided by

commissioned throughput below commissioned throughput;

In case Scheduler #1: licensed throughput divided by commissionedthroughput = 21Mbps / 42Mbps = 0.5

In case Scheduler #2: licensed throughput divided by commissionedthroughput = 105Mbps / 126Mbps = 0.83

0.5 is lower than 0.83, thus according to a), the remaining 21Mbps isallocated to Scheduler #1.

In result licensed throughput of Scheduler #1 is 42Mbps while licensedthroughput of Scheduler #2 is 105Mbps

If there are no HSDPA BTS Processing Sets licenses available, BTS sets 0Mbps as throughput to all schedulers.

For example:

In case when only one HSDPA processing set 1 or set 2 waspurchased, then the entire licensed throughput will be assigned to onescheduler (there is no more licensed throughput left for remainingschedulers).

In case when HSDPA processing set 3 was purchased, then the totallicensed throughput can be shared between multiple schedulers.





Confidential

Issue 01A

In case when there are not sufficient HSDPA licenses compared to thenumber of scheduler, not all schedulers might get HSDPA throughput.

For example:

The operator has two schedulers and 1 x HSDPA BTS Processing Set2. In this case, first scheduler gets 21Mbps and the second scheduler0Mbps.

2) HSDPA users:

The number of HSDPA licensed users is distributed among the available LCGs.

The HSDPA user amount is controlled on the BTS level and it can be dividedbetween LCGs according to the commissioned shares.

The operator has the possibility to select the dedicated HSDPA option duringBTS commissioning (HSDPA user share). This option defines the

guaranteed HSDPA user capacity for each LCG. The sum of all dedicated

options of the LCG cannot exceed 100%. If this sum is less than 100%, thenthe remaining part is common and all LCG can use those licenses on a needbasis.

If commissioning is not done, then the user amount will be divided equallybetween LCGs.

For example:

If one HSDPA BTS processing set 3 license was bought, the availableuser amount is 72 users. If one LCG is set, all numbers of users can betaken.

If one HSDPA BTS processing set three licenses were bought and twoLCGs were configured, the operator can commission, for example, 20%

of all available users to LCG1 and 40% to LCG2. This means that theremaining 40% is common for both LCGs and can be shared freelybetween them.

If no commissioning is done, the whole available amount of users isdivided equally per each configured LCG.

For more information on HSDPA BTS processing set capacities, see chapter2.2.2.

3.4 Associated UL/DL DCH

The associated UL/DL DCH of the HSDPA user requires the capacity in thesame way as a normal DCH. See table below.

User dataRel99 CE required

in UL / Min SFRel99 CE required

in DL / Min SF

PS 16 kbps 1/SF64* 1/SF128**

PS 64 kbps 4/SF16 1/SF128**

PS 128 kbps 4/SF8 1/SF128**







Confidential

Issue 01A

4 HSUPA and BTS dimensioningSome supported capacities mentioned in this document might require separatelicenses in the RAN before they can be activated. For more information, seeLicenses Management in WCDMA RAN.

For more specific information related to HSUPA, see HSUPA in BTS document

Baseband capacity is reserved for HSUPA on a need basis. The basebandcapacity allocation might be changed dynamically between DCH and HSUPAuse. In the baseband allocation, DCH has a higher priority than HSUPA. Theoperator might commission a minimum fixed reservation for HSUPA, but the restof the capacity is dynamically allocated to HSUPA when DCH does not need it.

HSUPA is supported only with the co-existence of HSDPA.

With System Module Rel.3 depending on commissioned LCG configuration type,HSUPA scheduler supports:

160 HSUPA users (Small HSPA configuration)

240 HSUPA users (Normal HSPA configuration)

Table below presents HSPA capabilities for different LCG configuration types(System Module Rel.3)

System Module Rel.3 Small HSPA conf iguration Normal HSPA conf iguration

Max number of HSPA cells 6 12

Number of HSDPAschedulers:

1 2

Max number of HSDPAusers

240 480

Number of HSUPAschedulers

1 1

Max number of HSUPA

users160 240

Table 12 Flexi System Module Rel.3 HSPA LCG propert ies

Only one HSUPA scheduler can be allocated per LCG.

The minimum HSUPA baseband allocation is 0 subunits. In this case, onlyHSUPA scheduler is active.

The operator can define the minimum HSUPA-reserved capacity to have theguaranteed service level.







Confidential

Issue 01A

4.1.1 HSUPA resource steps

HSUPA baseband resource allocation is done with specific sizes of resourcesteps. The amount of resources needed depends on the desired throughput andthe number of NRT HSUPA users.

HSUPA activation does not require fixed processing resources when the featureis being activated (at least one HSUPA BTS processing set and HSDPA BTSprocessing set is required)

To allocate the next HSUPA resource step, an additional free capacity of sixRel99 CE is needed. These six Rel99 CEs must be licensed in LCG basebandcapacity. The required 6 Rel99 CE free on top of the HSUPA resource step is toavoid a “ping-pong” effect in reserving and freeing HSUPA resource steps. Thisis needed so that the HSUPA resource step is not requested back immediatelyafter its allocation.

When free channel capacity drops below four CE, the Resource Manager startsto free resources used by HSUPA.

4.1.2 HSUPA resource allocation

HSUPA does not consume Rel99 CE licenses (even for SRB purpose). Themaximum baseband resources that can be allocated for HSUPA are defined byHSUPA BTS processing sets.

Baseband resources allocated for HSUPA purpose can change dynamically,based on current need (number of active users and combined L1 throughput ofall NRT HSUPA users). HSUPA baseband resource allocation is performed on astep basis. One HSUPA baseband resource is called a HSUPA resource step.

One HSUPA resource step consumes 0.125 subunit of a System Module Rel.3subunit.

System Module releaseSystem Module Rel.3

subunit

HSUPA resource stepbaseband capacity

0.125 subunit

Table 14 HSUPA resource step baseband capacity

If the total number of available R99 CE licenses and the number of HSUPAresources (described by the number of available HSUPA BTS processing sets)exceed the System Module capacity for traffic, the overlapping basebandcapacity can be dynamically exchanged between R99 and HSUPA users.

One HSUPA BTS Processing Set license (per LCG) provides 48 Rel99 CEcapacities without Rel.99 CE licenses.

Below figure is an example of a no-license overlapping scenario.





Confidential

Issue 01A

Figure 11 Example of baseband capacity reservation without license

overlapping

See Figure 16 for an example of System Module Rel.3 baseband capacityreservation with license overlapping.

Figure 12 Example of baseband capacity reservation with license

overlapping

For overlapping R99 CE licenses and licensed HSUPA resources (defined bythe number of available HSUPA BTS processing sets), commissioning can beperformed to guarantee resources for HSUPA. HSUPA resource commissioningis performed with two parameters - HSUPA BB decoding capacity Mbps

and HSUPA BB minimum users. Up to two HSUPA resource steps can be

statically commissioned for HSUPA.

Note that single HSUPA scheduler can also use the capacity of both basebandextension submodules (FBBA).





Confidential

Issue 01A

Table 15 HSUPA resource allocation in number of subunits for System Module Rel.3 (F-D

HSUPAdata UEs

per HSUPAscheduler

Baseband minimum decoding capacity [M

<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5

1 0.125 0.125 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A 2 0.125 0.125 0.125 0.25 N/A N/A N/A N/A N/A N/A N/A N/A

3~4 0.125 0.25 0.25 0.25 0.25 0.375 N/A N/A N/A N/A N/A N/A

5~6 0.125 0.25 0.25 0.25 0.25 0.375 0.375 0.5 N/A N/A N/A N/A

7~8 0.125 0.25 0.375 0.375 0.375 0.375 0.5 0.5 0.625 0.625 N/A N/A

9~10 0.125 0.25 0.375 0.5 0.5 0.5 0.5 0.625 0.75 0.75 0.75 0.75

11~12 0.25 0.25 0.375 0.5 0.5 0.5 0.5 0.625 0.75 0.75 0.875 0.875

13~14 0.25 0.375 0.375 0.5 0.625 0.625 0.625 0.625 0.75 0.75 0.875 0.875

15~16 0.25 0.375 0.5 0.5 0.625 0.75 0.75 0.75 0.75 0.75 0.875 0.875

17~18 0.25 0.375 0.5 0.5 0.625 0.75 0.75 0.75 0.75 0.75 0.875 0.875

19~20 0.25 0.375 0.5 0.625 0.75 0.75 0.875 0.875 0.875 0.875 0.875 0.875

21~22 0.375 0.375 0.5 0.625 0.75 0.875 0.875 0.875 0.875 0.875 0.875 0.87523~24 0.375 0.375 0.5 0.625 0.75 0.875 1 1 1 1 1 1

25~26 0.375 0.375 0.5 0.625 0.75 0.875 1 1.125 1.125 1.125 1.125 1.125

27~28 0.375 0.375 0.625 0.625 0.75 0.875 1 1.125 1.125 1.125 1.125 1.125

29~30 0.375 0.375 0.625 0.75 0.875 1 1.125 1.25 1.25 1.25 1.25 1.25

31~32 0.5 0.5 0.625 0.75 0.875 1 1.125 1.25 1.375 1.375 1.375 1.375

33~34 0.5 0.5 0.625 0.75 0.875 1 1.125 1.25 1.375 1.375 1.375 1.375

35~36 0.5 0.5 0.625 0.75 0.875 1 1.125 1.25 1.375 1.5 1.5 1.5

37~38 0.5 0.5 0.625 0.75 0.875 1 1.25 1.375 1.375 1.5 1.75 1.75

39~40 0.5 0 .5 0.625 0.75 1 1.125 1.25 1.375 1.5 1.625 1.75 1.75





Confidential

Issue 01A


HSUPAdata UEsper

HSUPAscheduler

Baseband minimum decoding capacity [Mbp

<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15

41~44 0.625 0.625 0.75 0.875 1 1.125 1.25 1.375 1.5 1.625 1.75 1.75 1.8

45~48 0.625 0.625 0.75 0.875 1 1.25 1.375 1.5 1.5 1.625 1.875 2 2

49~52 0.75 0.75 0.75 0.875 1.125 1.25 1.375 1.5 1.625 1.75 1.875 2 2

53~56 0.75 0.75 0.75 0.875 1.125 1.25 1.375 1.5 1.625 1.75 1.875 2 2

57~60 0.75 0.75 0.75 1 1.125 1.375 1.5 1.625 1.75 1.875 2 2.125 2.1

61~64 0.875 0.875 0.875 1 1.25 1.375 1.5 1.625 1.75 1.875 2 2.125 2.1

65~68 0.875 0.875 0.875 1.125 1.25 1.375 1.625 1.75 1.875 2 2.125 2.25 2.69~72 1 1 1 1.125 1.25 1.5 1.625 1.75 1.875 2 2.125 2.25 2.

73~76 1 1 1 1.125 1.25 1.5 1.625 1.75 2 2 2.125 2.375 2.3

77~80 1 1 1 1.125 1.375 1.5 1.75 1.875 2 2.125 2.25 2.375 2

81~100 1.25 1.25 1.25 1.25 1.5 1.75 1.875 2.125 2.25 2.375 2.5 2.625 2.

101~120 1.5 1.5 1.5 1.5 1.625 1.875 2.125 2.25 2.5 2.625 2.75 2.875 3

121~160 2 2 2 2 2 2.25 2.5 2.625 2.875 3 3.25 3.375 3

161~200 2.5 2.5 2.5 2.5 2.5 2.5 2.75 3 3.125 3.375 3.625 3.75 4

201~240 3 3 3 3 3 3 3 3.25 3.625 3.625 3.875 4.125 4.3





Confidential

Issue 01A

Table 15 HSUPA resource allocation in number of subunits for System Module Rel.3 (F

HSUPA dataUEs perHSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 3

1 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N


3~4 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N






15~16 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N17~18 1.25 1.25 N/A N/A N/A N/A N/A N/A N/A N/A N

19~20 1.25 1.25 1.5 1.5 N/A N/A N/A N/A N/A N/A N

21~22 1.25 1.25 1.5 1.5 1.75 1.75 N/A N/A N/A N/A N

23~24 1.25 1.25 1.5 1.5 1.75 1.75 2 2 N/A N/A N

25~26 1.25 1.25 1.5 1.5 1.75 1.75 2 2 2 2 N

27~28 1.25 1.25 1.5 1.5 1.75 1.75 2 2 2 2 2

29~30 1.5 1.75 1.75 1.75 1.75 1.75 2 2 2 2 2

31~32 1.5 1.75 1.75 1.75 1.75 1.75 2 2 2 2 2

33~34 1.5 1.75 1.75 1.75 1.75 1.75 2 2 2 2 2

35~36 2 2 2 2 2 2 2 2 2 2 2

37~38 2 2 2 2 2 2 2 2 2 2 239~40 2.25 2.25 2.5 2.5 2.625 2.625 2.625 2.75 2.75 2.75 2







Confidential

Issue 01A


HSUPAdata UEs

per HSUPAscheduler

Baseband minimum decoding capacity [Mbps

46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58 59.45 60.9 62.35

1 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

2 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

3~4 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A






15~16 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A17~18 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A







31~32 2.75 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

33~34 2.75 3 3 N/A N/A N/A N/A N/A N/A N/A N/A N/A

35~36 2.75 3 3 3.25 3.25 N/A N/A N/A N/A N/A N/A N/A

37~38 2.75 3 3 3.25 3.25 3.5 3.5 N/A N/A N/A N/A N/A39~40 3 3 3 3.25 3.25 3.5 3.5 3.75 3.75 N/A N/A N/A





Confidential

Issue 01A


HSUPAdata UEs

perHSUPA

scheduler


46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58 59.45 60.9 62.35

41~44 3 3 3 3.25 3.25 3.5 3.5 3.75 3.75 3.75 3.75 4

45~48 3 3 3 3.25 3.25 3.5 3.5 3.75 3.75 3.75 3.75 4

49~52 3 3 3 3.25 3.25 3.5 3.5 3.75 3.75 3.75 3.75 4

53~56 3 3 3 3.25 3.25 3.5 3.5 3.75 3.75 3.75 3.75 4

57~60 3 3 3 3.25 3.25 3.5 3.5 3.75 3.75 3.75 3.75 4

61~64 3 3 3 3.25 3.25 3.5 3.5 3.75 3.75 3.75 3.75 4

65~68 3 3 3 3.25 3.25 3.5 3.5 3.75 3.75 3.75 3.75 4

69~72 3 3 3 3.25 3.25 3.5 3.5 3.75 3.75 3.75 3.75 4

73~76 3 3 3 3.25 3.25 3.5 3.5 3.75 3.75 3.75 3.75 4

77~80 3.25 3.25 3.25 3.25 3.25 3.5 3.5 3.75 3.75 3.75 3.75 4

81~100 4 4 4 4 4 4 4 4 4 4 4 4

101~120 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75

121~160 6.125 6.25 6.375 6.375 6.375 6.375 6.375 6.375 6.375 6.375 6.375 6.375

161~200 6.625 6.75 6.875 7 7.125 7.25 7.375 7.5 7.625 7.75 7.875 7.875

201~240 7.125 7.25 7.375 7.5 7.625 7.75 7.875 8 8.125 8.25 8.375 8.5





Confidential

Issue 01A

Table 16 HSUPA resource allocation in number of subunits for System Module Rel.3 (non-F-DPCH 10ms

HSUPAdata UEs

per HSUPA

scheduler

Baseband minimum decoding capacity [M

<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5

1 0.125 0.125 0.125 N/A N/A N/A N/A N/A N/A N/A N/A N/A

2 0.125 0.125 0.25 0.25 N/A N/A N/A N/A N/A N/A N/A N/A

3~4 0.125 0.25 0.25 0.25 0.375 0.5 0.5 N/A N/A N/A N/A N/A

5~6 0.25 0.25 0.375 0.375 0.375 0.5 0.5 0.625 0.625 0.75 N/A N/A

7~8 0.25 0.25 0.375 0.375 0.375 0.5 0.5 0.625 0.75 0.875 1 1

9~10 0.25 0.375 0.375 0.5 0.5 0.5 0.625 0.625 0.75 0.875 1 1

11~12 0.375 0.375 0.375 0.5 0.625 0.625 0.625 0.625 0.75 0.875 1 1.125

13~14 0.375 0.375 0.5 0.5 0.625 0.625 0.625 0.75 0.75 0.875 1 1.125

15~16 0.5 0.5 0.5 0.5 0.75 0.75 0.75 0.75 0.75 0.875 1 1.125

17~18 0.5 0.5 0.5 0.625 0.75 0.875 0.875 0.875 0.875 0.875 1 1.125

19~20 0.5 0.5 0.5 0.625 0.75 0.875 0.875 0.875 0.875 0.875 1 1.125

21~22 0.625 0.625 0.625 0.625 0.75 1 1 1 1 1 1.125 1.125

23~24 0.625 0.625 0.625 0.75 0.875 1 1.125 1.125 1.125 1.125 1.125 1.125

25~26 0.75 0.75 0.75 0.75 0.875 1 1.125 1.125 1.125 1.125 1.25 1.25

27~28 0.75 0.75 0.75 0.75 0.875 1 1.125 1.25 1.25 1.25 1.25 1.375

29~30 0.75 0.75 0.75 0.75 1 1 1.125 1.25 1.375 1.375 1.375 1.5

31~32 0.875 0.875 0.875 0.875 1 1.125 1.25 1.375 1.375 1.375 1.5 1.5

33~34 0.875 0.875 0.875 0.875 1 1.125 1.25 1.375 1.5 1.5 1.5 1.625

35~36 0.875 0.875 0.875 1 1 1.125 1.25 1.375 1.5 1.625 1.625 1.625

37~38 1 1 1 1 1 1.125 1.25 1.5 1.5 1.625 1.625 1.75

39~40 1 1 1 1 1.125 1.25 1.375 1.5 1.625 1.75 1.75 1.875





Confidential

Issue 01A


HSUPAdata UEs

perHSUPA

scheduler


<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 1

41~44 1.125 1.125 1.125 1.125 1.125 1.25 1.375 1.5 1.625 1.75 1.875 1.875 1.

45~48 1.25 1.25 1.25 1.25 1.25 1.375 1.5 1.625 1.75 1.875 2 2.125 2.

49~52 1.375 1.375 1.375 1.375 1.375 1.375 1.5 1.625 1.75 1.875 2 2.125 2

53~56 1.5 1.5 1.5 1.5 1.5 1.5 1.625 1.75 1.875 2 2.125 2.25 2.

57~60 1.5 1.5 1.5 1.5 1.5 1.5 1.625 1.75 1.875 2 2.125 2.25 2.

61~64 1.625 1.625 1.625 1.625 1.625 1.625 1.75 1.875 2 2.125 2.25 2.375 2

65~68 1.75 1.75 1.75 1.75 1.75 1.75 1.75 1.875 2 2.125 2.25 2.375 2

69~72 1.875 1.875 1.875 1.875 1.875 1.875 1.875 2 2.125 2.25 2.375 2.5 2.73~76 2 2 2 2 2 2 2 2 2.125 2.25 2.375 2.5 2.

77~80 2 2 2 2 2 2 2 2.125 2.25 2.375 2.5 2.625 2

81~100 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.625 2.625 2.75 2.875

101~120 3 3 3 3 3 3 3 3 3 3 3.125 3.25 3.

121~160 4 4 4 4 4 4 4 4 4 4 4 4

161~200 5 5 5 5 5 5 5 5 5 5 5 5

201~240 6 6 6 6 6 6 6 6 6 6 6 6





Confidential

Issue 01A


HSUPAdata UEs

perHSUPA

scheduler

Baseband minimum decoding capacity [Mbps]

24.6 26.1 27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39

1 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/


3~4 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/





13~14 1.625 1.75 1.75 N/A N/A N/A N/A N/A N/A N/A N/15~16 1.75 1.875 1.875 2 2 2 N/A N/A N/A N/A N/

17~18 1.75 1.875 1.875 2 2.125 2.125 2.25 2.25 N/A N/A N/

19~20 1.75 1.875 2 2 2.125 2.25 2.25 2.375 2.375 2.5 2

21~22 1.875 1.875 2 2 2.125 2.25 2.25 2.375 2.5 2.5 2.6

23~24 1.875 1.875 2 2.125 2.125 2.25 2.375 2.375 2.5 2.625 2.6

25~26 1.875 2 2 2.125 2.25 2.25 2.375 2.375 2.5 2.625 2.

27~28 2 2 2.125 2.125 2.25 2.25 2.375 2.5 2.625 2.625 2.

29~30 2.125 2.125 2.125 2.125 2.25 2.375 2.5 2.5 2.625 2.625 2.

31~32 2.125 2.125 2.125 2.125 2.25 2.375 2.5 2.5 2.625 2.75 2.

33~34 2.125 2.25 2.25 2.25 2.25 2.375 2.5 2.5 2.625 2.75 2.8

35~36 2.125 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.837~38 2.125 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.8

39~40 2.125 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.8





Confidential

Issue 01A


HSUPAdata UEs

perHSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39

41~44 2.125 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.8

45~48 2.125 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.8

49~52 2.25 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.8

53~56 2.375 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.8

57~60 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.75 2.8

61~64 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.875 2.8

65~68 3 3 3 3 3 3 3 3 3 3 3

69~72 3.125 3.125 3.125 3.125 3.125 3.125 3.125 3.125 3.125 3.125 3.1

73~76 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.2

77~80 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.

81~100 3.75 3.875 4 4.125 4.25 4.25 4.25 4.25 4.25 4.25 4.2

101~120 4.125 4.25 4.375 4.5 4.625 4.75 4.875 5 5.125 5.125 5.1

121~160 4.75 4.875 5 5.125 5.25 5.375 5.5 5.625 5.75 5.875 6

161~200 5.375 5.5 5.625 5.75 5.875 6 6.125 6.25 6.375 6.5 6.6

201~240 6.125 6.125 6.25 6.375 6.5 6.625 6.875 7 7.125 7.25 7.3





Confidential

Issue 01A


HSUPAdata UEs

perHSUPA

scheduler


46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58 59.45 60.9 62.

1 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/

2 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/

3~4 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/





13~14 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/15~16 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/




23~24 3 3 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/

25~26 3.125 3.125 3.25 3.25 N/A N/A N/A N/A N/A N/A N/A N/

27~28 3.125 3.25 3.25 3.375 3.5 3.5 3.5 N/A N/A N/A N/A N/

29~30 3.125 3.25 3.375 3.375 3.5 3.5 3.625 3.75 3.75 3.75 N/A N/

31~32 3.125 3.25 3.375 3.375 3.5 3.625 3.75 3.75 3.875 3.875 4 4

33~34 3.25 3.25 3.375 3.5 3.625 3.625 3.75 3.75 3.875 4 4 4.1

35~36 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 3.875 4 4.125 4.137~38 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 3.875 4 4.125 4.1

39~40 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 4 4.125 4.125 4.1





Confidential

Issue 01A


HSUPAdata UEsper

HSUPAscheduler


46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58 59.4 60.9 62.3

41~44 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 4 4.125 4.125 4.25

45~48 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 4 4.125 4.125 4.2

49~52 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 4 4.125 4.125 4.2

53~56 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 4 4.125 4.125 4.2

57~60 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 4 4.125 4.125 4.2

61~64 3.25 3.375 3.5 3.5 3.625 3.75 3.75 3.875 4 4.125 4.125 4.25

65~68 3.375 3.375 3.5 3.625 3.625 3.75 3.875 3.875 4 4.125 4.125 4.25

69~72 3.375 3.5 3.5 3.625 3.75 3.75 3.875 4 4 4.125 4.125 4.25

73~76 3.375 3.5 3.625 3.625 3.75 3.75 3.875 4 4.125 4.125 4.25 4.25

77~80 3.5 3.5 3.625 3.625 3.75 3.875 3.875 4 4.125 4.25 4.25 4.37

81~100 4.25 4.25 4.25 4.25 4.25 4.25 4.25 4.25 4.25 4.375 4.5 4.5

101~120 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.12

121~160 6.625 6.75 6.875 6.875 6.875 6.875 6.875 6.875 6.875 6.875 6.875 6.87

161~200 7.25 7.375 7.5 7.625 7.75 7.875 8 8.125 8.25 8.375 8.5 8.5

201~240 8 8.125 8.125 8.25 8.375 8.625 8.625 8.75 8.875 9 9.125 9.25





Confidential

Issue 01A

Table 17 HSUPA resource allocation in number of subuni ts for System Module Rel.3 (F-DPCH 2ms TTI u

HSUPAdata UEs

per HSUPAscheduler


<1.0 1.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15.9 17.4 18.8

1 0.125 0.125 0.375 0.375 0.375 N/A N/A N/A N/A N/A N/A N/A N/A N/A2 0.125 0.125 0.375 0.375 0.375 0.375 0.625 0.625 0.625 N/A N/A N/A N/A N/A

3~4 0.125 0.25 0.5 0.5 0.625 0.75 0.75 0.75 0.75 0.75 0.75 0.875 1 1.37

5~6 0.125 0.25 0.5 0.5 0.625 0.75 0.875 1 1 1 1 1 1 1.37

7~8 0.125 0.25 0.5 0.5 0.625 0.875 0.875 1 1.25 1.375 1.375 1.375 1.375 1.37

9~10 0.125 0.25 0.5 0.5 0.625 0.875 1 1 1.25 1.375 1.375 1.625 1.625 1.62

11~12 0.25 0.25 0.5 0.5 0.625 0.875 1 1 1.25 1.375 1.375 1.625 1.75 1.75

13~14 0.25 0.25 0.5 0.625 0.625 0.875 1 1 1.25 1.375 1.375 1.625 1.75 1.75

15~16 0.25 0.375 0.5 0.625 0.625 0.875 1 1 1.25 1.375 1.375 1.625 1.75 1.75

17~18 0.25 0.375 0.5 0.75 0.75 0.875 1 1 1.25 1.375 1.375 1.625 1.75 1.7

19~20 0.25 0.375 0.5 0.75 0.75 0.875 1 1 1.25 1.375 1.375 1.625 1.75 1.75

21~22 0.375 0.375 0.5 0.75 0.875 0.875 1 1 1.25 1.375 1.375 1.625 1.75 1.75

23~24 0.375 0.375 0.5 0.75 1 1 1 1 1.25 1.375 1.375 1.625 1.75 1.75

25~26 0.375 0.375 0.5 0.75 1 1 1 1 1.25 1.375 1.375 1.625 1.75 1.75

27~28 0.375 0.375 0.625 0.75 1 1.125 1.25 1.25 1.25 1.375 1.375 1.625 1.75 1.75

29~30 0.375 0.375 0.625 0.75 1 1.125 1.25 1.25 1.25 1.375 1.375 1.625 1.75 1.75

31~32 0.5 0.5 0.625 0.75 1 1.125 1.25 1.25 1.25 1.375 1.375 1.625 1.75 1.75

33~34 0.5 0.5 0.625 0.75 1 1.125 1.375 1.375 1.375 1.375 1.375 1.625 1.75 1.75

35~36 0.5 0.5 0.625 0.75 1 1.25 1.375 1.5 1.5 1.5 1.5 1.625 1.75 1.75

37~38 0.5 0.5 0.625 0.875 1 1.25 1.375 1.5 1.5 1.5 1.5 1.625 1.75 1.75

39~40 0.5 0.5 0.75 0.875 1 1.25 1.375 1.625 1.625 1.625 1.625 1.625 1.75 1.75





Confidential

Issue 01A

Table 16 HSUPA resource allocation in number of subunits for System Module Rel.3 (F-DPCH 2ms TTI u

HSUPAdata UEs

per HSUPAscheduler


<1.0 1.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15.9 17.4 18.8

41~44 0.625 0.625 0.75 0.875 1 1.25 1.375 1.625 1.75 1.75 1.75 1.75 1.75 1.75

45~48 0.625 0.625 0.75 0.875 1 1.25 1.375 1.625 1.875 1.875 1.875 1.875 1.875 1.87

49~52 0.75 0.75 0.875 1 1 1.25 1.5 1.625 1.875 2 2 2 2 2

53~56 0.75 0.75 0.875 1 1.125 1.25 1.5 1.625 1.875 2 2.25 2.25 2.25 2.25

57~60 0.75 0.75 0.875 1 1.125 1.25 1.5 1.625 1.875 2 2.25 2.375 2.375 2.37

61~64 0.875 0.875 0.875 1.125 1.125 1.375 1.5 1.625 1.875 2 2.25 2.5 2.5 2.5

65~68 0.875 0.875 0.875 1.125 1.25 1.375 1.5 1.75 1.875 2.125 2.25 2.5 2.625 2.62

69~72 1 1 1 1.125 1.25 1.375 1.5 1.75 1.875 2.125 2.25 2.5 2.625 2.87

73~76 1 1 1 1.25 1.25 1.375 1.5 1.75 2 2.125 2.25 2.5 2.625 2.8777~80 1 1 1 1.25 1.375 1.5 1.625 1.75 2 2.125 2.375 2.5 2.75 2.87

81~100 1.25 1.25 1.25 1.25 1.625 1.625 1.75 1.875 2 2.25 2.375 2.625 2.75 3

101~120 1.5 1.5 1.5 1.5 1.625 1.875 2 2.125 2.25 2.375 2.5 2.75 2.875 3.12

121~160 2 2 2 2 2 2 2.5 2.5 2.625 2.75 2.875 3 3.125 3.25

161~200 2.5 2.5 2.5 2.5 2.5 2.5 2.5 3.125 3.125 3.125 3.25 3.375 3.5 3.62

201~240 3 3 3 3 3 3 3 3.125 3.125 3.625 3.625 3.75 3.875 4





Confidential

Issue 01A


HSUPAdata UEs

perHSUPA

scheduler


27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42




5~6 1.625 1.75 2 2 2 2 N/A N/A N/A N/A N/

7~8 1.625 1.75 2 2 2 2 2 2.125 2.375 2.625 2.6

9~10 1.625 1.75 2 2 2 2 2 2.125 2.375 2.625 2.6

11~12 2 2 2 2 2 2 2 2.125 2.375 2.625 2.6

13~14 2.25 2.25 2.25 2.25 2.25 2.25 2.25 2.25 2.375 2.625 2.615~16 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.6

17~18 2.625 2.75 2.875 2.875 2.875 2.875 2.875 2.875 2.875 2.875 2.8

19~20 2.625 2.75 2.875 3 3 3.25 3.25 3.25 3.25 3.25 3.2

21~22 2.625 2.75 2.875 3 3 3.25 3.25 3.5 3.5 3.5 3.

23~24 2.625 2.75 2.875 3 3 3.25 3.375 3.5 3.5 3.75 3.8

25~26 2.625 2.75 2.875 3 3 3.25 3.375 3.5 3.5 3.75 3.8

27~28 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.8

29~30 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.8

31~32 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.8

33~34 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.8

35~36 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.8

37~38 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.8

39~40 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.8





Confidential

Issue 01A


HSUPA dataUEs perHSUPA

scheduler

Baseband minimum decoding capacity [Mb

27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6

41~44 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3

45~48 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3

49~52 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3

53~56 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3

57~60 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3

61~64 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3

65~68 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3

69~72 2.875 2.875 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3

73~76 3 3 3 3 3.125 3.25 3.375 3.5 3.625 3.75 377~80 3.125 3.125 3.125 3.125 3.125 3.25 3.375 3.5 3.625 3.75 3

81~100 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3

101~120 4.25 4.375 4.625 4.625 4.625 4.625 4.625 4.625 4.625 4.625 4

121~160 4.375 4.625 4.75 5 5.125 5.375 5.5 5.75 5.875 6.125 6

161~200 4.5 4.75 4.875 5.125 5.375 5.5 5.75 5.875 6.125 6.25

201~240 4.75 4.875 5 5.25 5.5 5.625 5.875 6 6.25 6.5 6







Confidential

Issue 01A


HSUPAdata UEs

perHSUPA

scheduler


49.2 50.7 52.2 53.6 55.0 56.5 58 59.4 60.9 62.35 63

41~44 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.

45~48 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.

49~52 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.

53~56 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.

57~60 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.

61~64 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.65~68 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.

69~72 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.

73~76 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.

77~80 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.

81~100 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.

101~120 4.625 4.625 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.

121~160 6.125 6.125 6.125 6.125 6.125 6.125 6.125 6.125 6.125 6.125 6.1

161~200 7.375 7.625 7.625 7.625 7.625 7.625 7.625 7.625 7.625 7.625 7.6

201~240 7.5 7.75 8 8.125 8.375 8.5 8.625 8.875 9 9.125 9.1





Confidential

Issue 01A

Table 18 HSUPA resource allocation in number of subuni ts for System Module Rel.3 (non-F-DPCH 2ms

HSUPAdata UEs

per HSUPA

scheduler


<1.0 1.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15.9 17.4 18.8

1 0.125 0.125 0.375 0.375 0.375 N/A N/A N/A N/A N/A N/A N/A N/A N/A

2 0.125 0.125 0.375 0.375 0.375 0.375 0.625 0.625 0.625 N/A N/A N/A N/A N/A

3~4 0.125 0.25 0.5 0.5 0.625 0.75 0.75 0.75 0.75 0.75 0.75 0.875 1 1.37

5~6 0.125 0.25 0.5 0.5 0.625 0.75 0.875 1 1 1 1 1 1 1.37

7~8 0.125 0.25 0.5 0.5 0.625 0.875 0.875 1 1.25 1.375 1.375 1.375 1.375 1.37

9~10 0.125 0.25 0.5 0.5 0.625 0.875 1 1 1.25 1.375 1.375 1.625 1.625 1.62

11~12 0.25 0.25 0.5 0.5 0.625 0.875 1 1 1.25 1.375 1.375 1.625 1.75 1.75

13~14 0.25 0.25 0.5 0.625 0.625 0.875 1 1 1.25 1.375 1.375 1.625 1.75 1.75

15~16 0.25 0.375 0.5 0.625 0.625 0.875 1 1 1.25 1.375 1.375 1.625 1.75 1.75

17~18 0.25 0.375 0.5 0.75 0.75 0.875 1 1 1.25 1.375 1.375 1.625 1.75 1.7

19~20 0.25 0.375 0.5 0.75 0.75 0.875 1 1 1.25 1.375 1.375 1.625 1.75 1.75

21~22 0.625 0.625 0.75 0.875 1 1 1 1.125 1.25 1.375 1.5 1.625 1.75 2

23~24 0.625 0.625 0.75 0.875 1 1.125 1.125 1.125 1.25 1.375 1.5 1.625 1.75 2

25~26 0.75 0.75 0.75 1 1 1.125 1.125 1.125 1.25 1.375 1.5 1.625 1.75 2

27~28 0.75 0.75 0.875 1 1.125 1.25 1.25 1.25 1.25 1.375 1.5 1.625 1.75 2

29~30 0.75 0.75 0.875 1 1.125 1.25 1.375 1.375 1.375 1.375 1.5 1.625 1.75 2

31~32 0.875 0.875 0.875 1 1.125 1.25 1.375 1.375 1.375 1.375 1.5 1.625 1.75 2

33~34 0.875 0.875 1 1.125 1.25 1.375 1.5 1.5 1.5 1.5 1.5 1.625 1.75 2

35~36 0.875 0.875 1 1.125 1.25 1.375 1.5 1.625 1.625 1.625 1.625 1.625 1.75 2

37~38 1 1 1 1.125 1.25 1.375 1.5 1.625 1.625 1.625 1.625 1.625 1.75 2

39~40 1 1 1.125 1.25 1.375 1.5 1.625 1.75 1.75 1.75 1.75 1.75 1.75 2





Confidential

Issue 01A


HSUPAdata UEs

per HSUPAscheduler


<1.0 1.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15.9 17.4 18.8

41~44 1.125 1.125 1.125 1.25 1.375 1.5 1.625 1.75 1.875 1.875 1.875 1.875 1.875 2

45~48 1.25 1.25 1.25 1.375 1.5 1.625 1.75 1.875 2 2.125 2.125 2.125 2.125 2.12

49~52 1.375 1.375 1.375 1.375 1.5 1.625 1.75 2 2 2.125 2.25 2.25 2.25 2.25

53~56 1.5 1.5 1.5 1.5 1.625 1.75 1.875 2 2.125 2.25 2.375 2.375 2.375 2.37

57~60 1.5 1.5 1.5 1.625 1.75 1.875 2 2.125 2.25 2.375 2.5 2.625 2.625 2.62

61~64 1.625 1.625 1.625 1.625 1.75 1.875 2 2.125 2.25 2.375 2.5 2.625 2.75 2.7

65~68 1.75 1.75 1.75 1.75 1.875 2 2.125 2.25 2.375 2.5 2.625 2.75 2.875 2.87

69~72 1.875 1.875 1.875 1.875 2 2 2.25 2.25 2.375 2.625 2.625 2.875 2.875 3.12

73~76 2 2 2 2 2 2.125 2.25 2.375 2.5 2.625 2.75 2.875 3 3.1277~80 2 2 2 2 2.125 2.25 2.375 2.5 2.625 2.75 2.875 3 3.125 3.25

81~100 2.5 2.5 2.5 2.5 2.5 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.62

101~120 3 3 3 3 3 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4

121~160 4 4 4 4 4 4 4 4 4.125 4.25 4.375 4.5 4.625 4.75

161~200 5 5 5 5 5 5 5 5 5 5 5.125 5.25 5.375 5.5

201~240 6 6 6 6 6 6 6 6 6 6 6 6 6.125 6.25





Confidential

Issue 01A

Table 17 HSUPA resource allocation in number of subuni ts for System Module Rel.3 (non-F-DPCH 2ms

HSUPAdata UEs

perHSUPA

scheduler


27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42

1 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

2 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

3~4 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

5~6 1.625 1.75 2 2 2 2 N/A N/A N/A N/A N/A

7~8 1.625 1.75 2 2 2 2 2 2.125 2.375 2.625 2.62

9~10 1.625 1.75 2 2 2 2 2 2.125 2.375 2.625 2.62

11~12 2 2 2 2 2 2 2 2.125 2.375 2.625 2.62

13~14 2.25 2.25 2.25 2.25 2.25 2.25 2.25 2.25 2.375 2.625 2.6215~16 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.62

17~18 2.625 2.75 2.875 2.875 2.875 2.875 2.875 2.875 2.875 2.875 2.87

19~20 2.625 2.75 2.875 3 3 3.25 3.25 3.25 3.25 3.25 3.2

21~22 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.625 3.62

23~24 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4

25~26 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4

27~28 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4

29~30 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4

31~32 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4

33~34 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4

35~36 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4

37~38 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4

39~40 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4





Confidential

Issue 01A


HSUPAdata UEs

perHSUPA

scheduler


27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6

41~44 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875

45~48 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875

49~52 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875

53~56 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875

57~60 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875

61~64 2.75 2.875 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875

65~68 3 3 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875

69~72 3.125 3.125 3.125 3.125 3.25 3.25 3.375 3.625 3.625 3.875 73~76 3.25 3.25 3.25 3.25 3.375 3.375 3.375 3.625 3.625 3.875

77~80 3.375 3.375 3.375 3.5 3.5 3.5 3.5 3.625 3.625 3.875

81~100 4.25 4.25 4.25 4.25 4.25 4.25 4.25 4.25 4.25 4.25 4

101~120 4.75 4.875 5 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5

121~160 5.5 5.625 5.75 5.875 6 6.125 6.25 6.375 6.5 6.75 6

161~200 6.25 6.375 6.5 6.625 6.75 6.875 7 7.125 7.25 7.375 7

201~240 7 7.125 7.25 7.375 7.5 7.625 7.75 7.875 8 8.125 8





Confidential

Issue 01A


HSUPAdata UEs

perHSUPA

scheduler


49.2 50.7 52.2 53.6 55.0 56.5 58 59.4 60.9 62.35 63






9~10 2.875 3.125 3.125 3.125 3.375 3.375 3.375 N/A N/A N/A N

11~12 2.875 3.125 3.125 3.125 3.375 3.375 3.375 3.5 3.625 3.625 3.6

13~14 2.875 3.125 3.125 3.125 3.375 3.375 3.375 3.5 3.625 3.625 3.615~16 2.875 3.125 3.125 3.125 3.375 3.375 3.375 3.5 3.625 3.625 3.6

17~18 2.875 3.125 3.125 3.125 3.375 3.375 3.375 3.5 3.625 3.625 3.6

19~20 3.25 3.25 3.25 3.25 3.375 3.375 3.375 3.5 3.625 3.625 3.6

21~22 3.625 3.625 3.625 3.625 3.625 3.625 3.625 3.625 3.625 3.75 3.

23~24 4 4 4 4 4 4 4 4 4 4

25~26 4.25 4.25 4.25 4.25 4.25 4.25 4.25 4.25 4.25 4.25 4

27~28 4.625 4.625 4.625 4.625 4.625 4.625 4.625 4.625 4.625 4.625 4.6

29~30 4.625 4.75 4.875 4.875 4.875 4.875 4.875 4.875 4.875 4.875 4.8

31~32 4.625 4.75 4.875 5 5.25 5.25 5.25 5.25 5.25 5.25 5

33~34 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.5 5.5 5

35~36 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.75 5.8

37~38 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.8

39~40 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.8





Dimensioning WCDMA RAN: Flexi BTS Baseband


Confidential

Issue 01A

In Table 15, Table 16, Table 16 and Table 17 the assumption is that the HSUPAlicensed capacity is limited, as well as the typical use case when the majority of the users

are DL data dominated and the remaining users are UL data dominated.

No more than 16.875 subunits can be allocated for HSUPA per single System ModuleRel.3

LCG conf iguration type FSMF FSMF + FBBA FSMF + 2xFBBA

Small HSPA 4,875 10,875 16,875

Normal HSPA 4,375 10,375 16,575

Table 19 Max number of HSUPA subunits wi th System Module Rel.3

If more than 160 (Small HSPA configuration) / 240 (Normal HSPA configuration) HSUPAusers per single System Module Rel.3 are required, then the second LCG needs to becreated.

To calculate the subunits reservation inside Rel.3 System Module for mixed user typecase, (F-DPCH/no-FDPCH/2ms TTI/10msTTI users and CS Voice over HSPA), thefollowing rule should be applied.

In some cases, the rule presented below leads to overestimation of baseband resources.

HSUPA_Subunits = F-DPCH_2msTTI_Subunits +

F-DPCH_10msTTI_Subunits + no-FDPCH_2msTTI_Subunits +

no-FDPCH_10msTTI_Subunits + CS_Voice_over _HSPA_Subunits

Equation 7 HSUPA subunits formula

where:

F-DPCH_2msTTI_Subunits – subunits required for HSUPA F-DPCH 2ms TTIusers (including data and CS Voice over HSPA users), calculated from Table 24;

F-DPCH_10msTTI_Subunits – subunits required for HSUPA F-DPCH 10ms TTIusers (including data and CS Voice over HSPA users), calculated from Table 26;

No-F-DPCH_2msTTI_Subunits – subunits required for HSUPA no-F-DPCH 2msTTI users, calculated from Table 25;

No-F-DPCH_10msTTI_Subunits – subunits required for HSUPA no-F-DPCH10ms TTI users, calculated from Table 27;

CS_Voice_over_HSPA_Subunits – subunits required for CS Voice over HSPAusers.

For example:

System Module Rel.3 in use;

HSUPA BTS combined L1 throughput = 28Mbps;





Confidential

Issue 01A

Number of F-DPCH 2ms TTI users = 8 UEs with 7Mbps throughput;

Number of F-DPCH 10ms TTI users = 18 UEs with 7Mbps throughput;

Number of no-F-DPCH 2ms TTI users = 22 UEs with 7Mbps throughput;

Number of no-F-DPCH 10ms TTI users = 34 UEs with 7Mbpsthroughput;

.

F-DPCH_2msTTI_Subunits – 0.875 subunit required; see Table 24 (eight users,7Mbps combined L1 thr);

F-DPCH_10msTTI_Subunits –0.75 subunit required; see Table 26 (18 users,7.2Mbps combined L1 thr);

No-F-DPCH_2msTTI_Subunits – 1 subunit required; see Table 25 (22 users,7Mbps combined L1 thr);

No-F-DPCH_10msTTI_Subunits – 1.25 subunit required; see Table 27 (34users, 7.2Mbps combined L1 thr);

According to

Equation 7 HSUPA_subunits = 0.875 + 0.75 + 1 + 1.25

= 3,875

Therefore: 3,875 subunits for HSUPA users are required.

4.1.3 Interference Cancellation uni t (PIC pool)

To achieve high HSUPA throughput, the interference cancellation feature isrecommended. Interference cancellation is performed with PIC pool units. With thecommissioning parameter, the operator can activate the required number of PIC pools,and then perform cell mapping to the PIC pools.

PIC pool unit is LCG specific therefore it can provide interference cancelation for HSUPAcells dedicated to LCG where PIC pool unit and HSPA schedulers resources areallocated.

Up to six cells (with 2 way Rx diversity) can be mapped to one PIC pool unit andinterference cancellation is performed in six cells at the same time.

4-way Rx diversity is not supported with Interference Cancellation feature.

Cells from the same frequency layer (LCG) should be mapped to the same PIC pool unit.

Up to two frequency layers are supported by one PIC pool.

One PIC pool unit consumes one subunit capacity.

Interference Cancellation unit (PIC pool) summary information





Confidential

Issue 01A

The table below contains the summary information related to PIC pool unit.

PIC pool unit parameters 2 way Rx diversity

Max number of cells supported by singlePIC pool unit

6

Max number of cells with simultaneousinterference cancellation performed by

single PIC pool unit6

Max number of PIC pools per SystemModule

3

Max number of carriers supported bysingle PIC pool

2

Table 20 PIC pool unit summary information

4.1.4 CS Voice over HSPA users allocation

CS Voice over HSPA users consumes subunit capacity.

With System Module Rel.3 up to 80 CS Voice over HSPA users can be allocated in onesubunit.

Number of CS Voice over HSPAusers

Subunit (SystemModule Rel.3)

10 0.125

20 0.25

30 0.375

40 0.5

50 0.625

60 0.75

70 0.875

80 1

Table 21 CS Voice over HSPA users (System Module Rel.3)

NOTE:

CS voice over HSPA users do not consume Rel99 CE licenses.





Confidential

Issue 01A

A CS voice over HSPA user has the same priority as an HSPA user.

Each CS voice over HSPA user decreases the number of HSUPA users allowed by theHSUPA license (HSUPA processing set) and the HSDPA license (HSDPA processingset).

CS voice over HSPA user consumes HSDPA and HSUPA scheduler resources, forexample, decreases the maximum number of HSPA users by one

CS Voice over HSPA users are allocated in the baseband capacity licensed for HSUPA.

For more specific information about CS Voice over HSPA feature, see RAN1689: CSVoice over HSPA feature description.

4.1.5 E-TFCI table selection

E-DCH Transport Format Combination Indicator (E-TFCI) corresponds to single TransportBlock Size (TBS) transmitted within E-DPCH in single TTI. E-TFCI table is a set of TBSs,which can be selected for E-DCH transmission. In case 10ms TTI transmission 3GPPdefines two E-TFCI tables:

- E-TFCI Table 0,- E-TFCI Table 1;

For 10ms TTI transmission with configured F-DPCH channel (RAN1201 FractionalDPCH), it is recommended to use E-TFCI Table 1. Otherwise, if E-TFCI Table 0 isconfigured for 10ms TTI HSUPA users with F-DPCH channel, the amount of HSUPAusers in baseband gets limited. For E-TFCI Table 1, baseband can support 60% lessusers than in E-TFCI Table 0. Decoding capacity of a low data rate user with E-TFCITable 0 is affected, as in this case user consumes more baseband resources than a userwith E-TFCI Table 1. As a result, less resources are available for high data rate users.

For low data rates (single Mac-d PDU) and E-TFCI Table 0, the smallest physical channelfor sending one MAC-d PDU in a TTI is limited to Spreading Factor 16 (SF16). It is limitedby coding rate, which has constant threshold value in 3GPP. E-TFCI Table 1 allowsusage of physical channel SF32. Physical channel SF16 requires roughly double baseband resources compared to SF32 and thus it has direct impact on the amount of usersthat can be allocated.

Note that if SF16 or higher physical channel is not allowed then coding rate is allowed toget smaller values and SF32 is possible for one MAC-d PDU also with E-TFCI table 0.

To configure E-TFCI Table 1 for 10ms FDPCH E-DCH transmission, RNC PRFILEparameter needs to be modified (available from RU30EP2). Refer to WCDMA RAN and I-HSPA RRM HSUPA document for E-TFCI table configuration details.

4.1.6 HSUPA BTS Processing Set resources allocation

Each HSUPA BTS processing set license increases the LCG’s maximum user amount bytwenty four users and the available throughput by 5.8Mbps. For example, if two HSUPABTS processing sets were bought, then up to 2x5.8Mbps = 11.6Mbps throughput will be





Confidential

Issue 01A

supported and up to 2x24 users = 48 users. Note that also an ASW license might beneeded to reach a certain throughput or amount of users.

In RU30, the HSUPA license (HSUPA BTS processing set) does not assure maximumthroughput to all users simultaneously, but it provides maximum throughput (5.8Mbps) toone user and minimum throughput to all 24 users. Therefore, to calculate the requirednumber of HSUPA BTS processing sets for certain number of users and throughputvalue, it is recommended to use the following formula:

Number_of_HSUPA_BTS_Processing_Sets

max {

Roundup ((F-DPCH_2msTTI_Subunits + F-DPCH_10msTTI_Subuni ts

+ no-FDPCH_2msTTI_Subunits + no-FDPCH_10msTTI_Subunits +CS_Voice_over_HSPA_Subuni ts) / 0.75 ); Minimum number of HSUPA BTSProcessing Sets };

Equation 8 Number of HSUPA BTS Process ing Sets fo r HSUPA users

where:

F-DPCH_2msTTI_Subunits – subunits required for HSUPA F-DPCH 2ms TTIusers, calculated from Table 24;

F-DPCH_10msTTI_Subunits – subunits required for HSUPA F-DPCH 10ms TTIusers, calculated from Table 26;

No-F-DPCH_2msTTI_Subunits – subunits required for HSUPA no-F-DPCH 2msTTI users, calculated from Table 25;

No-F-DPCH_10msTTI_Subunits – subunits required for HSUPA no-F-DPCH10ms TTI users, calculated from Table 27;

CS_Voice_over_HSPA_Subunits – subunits required for CS Voice overHSPA users. Minimum number of HSUPA BTS Processing Sets –Minimum number of HSUPA BTS Processing Set licenses calculatedwith Equation 9

Minimum_Number_of_HSUPA_BTS_Processing_Sets = max {

Roundup (HSUPA_users / 24); Roundup (HSUPA_throughput / 5.8) };Equation 9 Minimum number of HSUPA BTS Processing Sets

Exemplary calculation of required number of HSUPA Processing Sets with SystemModule Rel.3:

After baseband dimensioning (done using





Confidential

Issue 01A

Equation 7, for more information see previous example) it occurs that 3,875subunits in total are required for HSUPA users (82 HSUPA data users/combined

L1 throughput = 28Mbps);

Using Equation 8 and Equation 9 Number of HSUPA BTS Processing Sets =max (roundup(3.875 / 0,75) ; roundup (82 / 24) ; roundup(28 / 5,8) ) = max(roundup(5.17); roundup(3.41); roundup(4.8) ) = max( 6 ; 4 ; 5) = 6;

The required throughput and number of active HSUPA users can beachieved simultaneously.

If Baseband pooling is used then BTS will divide the HSUPA licenses between LCGsaccording to the commissioned share (shareOfHSUPALicences ). The sum of LCG

shares is always 100%. HSUPA license share is performed with HSUPA BTS processingset license granularity. If licenses cannot be shared equally between LCGs, the BTS willdivide the higher amount of licenses to the LCG starting from the lowest LCG number.For example, if commissioned shares are 50%/50%, and there are five HSUPA licenses,then LCG1 gets three licenses and LCG2 gets two licenses.





Confidential

Issue 01A

5 Extended cell in Flexi WCDMA

BTSThe basic principles for Extended Cell in WCDMA BTS are as follows:

- A cell is called an Extended Cell when its radius is >20km;- Cells with radius ≤ 20km are treated according to normal baseband

dimensioning rules;- Additional resources need to be calculated separately for each Extended Cell.

For example, if there is a 1+1+1 configuration, with 1 * 20km cell and 2 * 100km cell, it isneeded to calculate 1* 20km cell according to normal common channel dimensioningrules and 2 *100 km cells according to Extended Cell dimensioning rules.

- Extended cell baseband dimensioning rules are the same for all WCDMA

frequencies.- One or several of the cells in the BTS (supported configurations) can beconfigured as Extended Cells.

For more specific information about extended cell feature, see RAN1127: Extended Cell(180km) feature description

5.1 Extended cell dimensioning details

Extended Cell Common Control Channel dimensioning rules for Flexi WCDMA BTS areas follows:

Required baseband resources for Flexi System Module Rel. 3:

The number of baseband resources (CCCH pools) required for the Extended Celldepends on cell range and site configuration. One Extended Cell with range up to 180kmcan be served with CCCH pool (0.5 subunit). However, if a lower cell radius is required,more than one Extended Cell can be served with one CCCH pool or the Extended Cellcan be served together with normal cells using CCCH resources included in the SystemModule Rel.3 capacity. Note that each CCCH pool requires CCCH Processing Set foractivation.





Confidential

Issue 01A

For example:

1+1/10km + 1/40km (2way Rx div) – 1 CCCH pool (1 CCCH Processing Setlicense) required for CCCH

2+2/10km + 2/40km (2way Rx div) – 1 CCCH pool (1 CCCH Processing Setlicense) required for CCCH

Other site configurations that can be served with the single CCCH pool can bedetermined with the formula below:

cellsof

i

_ _ #

1

ii 480Rx)*Signaturesof #*Range(Cell

where:

i – number of cells (from 1 to 6);

Cell range – user cell radius stated in kilometers (rounded up to the wholekilometer that is divisible by five);

# of Signatures - means the maximum number of Preamble signatures 1=< z =< 4

where:

2-way Rx div:




4-way Rx div:




Rx – {2 ; 4} for 4 way Rx diversity Rx= 4, otherwise Rx =2





Confidential

Issue 01A

6 Multi RAB

Multi RAB call is a single user call with multiple (up to four) services (RABs) activesimultaneously. For example UE actively downloading data via HSDPA service whilehaving 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;

For more specific information about MultiRAB calls, see WCDMA RAN and Flexi Direct:

BTS RRM HSDPA, and WCDMA RAN and Flexi Direct: BTS RRM HSUPA document.

6.1 HSDPA + AMR call resource allocation

If UE has active HSDPA service (UL: Rel.99, DL: HSDPA) while AMR on DCH service isestablished, Rel99 CE resources for the AMR service are allocated. DCH service of MultiRAB call consumes Rel99 CE licenses in UL/DL for DCH processing.

6.2 HSUPA + AMR call resource allocationIf AMR DCH service is established while UE has an active HSUPA service (UL:HSUPA,DL: HSDPA), the AMR service is processed with already allocated HSUPA resources. AMR service of Multi RAB call does not require any additional baseband resources forprocessing, nor Rel99 CE licenses in UL/DL are required.

AMR service of a Multi RAB call is processed on the same System Module where anongoing HSPA service of a Mutli RAB call is processed.

Set up of an AMR service with ongoing HSPA connection might have an impact onavailable baseband resources depending whether FDPCH feature is actively used by theUE:



Documents

Dimension WCDMA