wran dim flexi bts bb-0900d80580a2180a

WCDMA RAN, Rel. RU40, Operating Documentation, Issue 05

Dimensioning WCDMA RAN: Flexi BTS Baseband DN0981084 Issue 02D Approval date: 2014-03-14

Dimensioning WCDMA RAN: Flexi BTS Baseband Disclaimer

DN0981084 Issue 02D

Copyright © 2014 Nokia Solutions and Networks All rights reserved.

DND 2 (128)))

Disclaimer

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Solutions and Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Solutions and Networks will, if deemed necessary Nokia Solutions and Networks, explain issues which may not be covered by the document. Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Solutions and Networks 2014. All rights reserved.

Table of contents

Dimensioning WCDMA RAN: Flexi BTS Baseband

3 (128)))


DND DN0981084 Issue 02D

Table of contents

Table of contents ................................................................................... 3

Summary of changes ............................................................................ 5

1 Introduction .......................................................................... 6

2 Multiradio Flexi BTS WCDMA ............................................. 7

2.1 Flexi BTS HW release mixed configurations ........................ 11

2.2. Flexi Multiradio 10 BTS system module capacity ................ 11

All values in the tables above were calculated according to Equation 10 presented in chapter 6.1 ................................................. 16

2.3. Flexi Multimode BTS system module capacity .................... 17

2.4. Baseband allocation basics ................................................. 19

2.5. Common Control Channels .................................................. 21

2.5.1. CCCH requirements for Multiradio 10 BTS system modules ................................................................................ 22

2.5.2. CCCH requirements for Multimode System Modules .......... 24

2.6. Capacity licenses ................................................................. 25

2.7. Local Cell Grouping for Flexi BTS ........................................ 27

2.8. Dedicated Channels ............................................................. 29

2.8.1. Asymmetric UL/DL Rel99 CE allocation .............................. 31

3 HSDPA and BTS dimensioning ........................................ 32

3.1 Flexi System Module Rel.3 HSDPA scheduler .................... 32

3.2 Flexi System Module Rel.2 HSDPA scheduler .................... 34

3.3 Tcell grouping with System Module Rel.2 and System Module Rel.3 ........................................................................ 39

3.4 HSDPA BTS Processing Set resources allocation .............. 40

3.5 Associated UL/DL DCH ........................................................ 43

4 HSUPA and BTS dimensioning ........................................ 44

4.1 HSUPA users baseband allocation principles ...................... 46

4.1.1 HSUPA resource steps ........................................................ 46

4.1.2 HSUPA resource allocation.................................................. 46

4.1.3 Hybrid Processing Set .......................................................... 48

4.1.4 HSUPA Resource utilization – dimensioning approach ....... 51

4.1.5 Static HSUPA resources allocation ...................................... 95

4.1.6 Interference Cancellation unit (PIC pool) ............................. 96

Dimensioning WCDMA RAN: Flexi BTS Baseband Table of contents

DN0981084 Issue 02D


DND 4 (128)))

4.1.7 HS Cell_FACH users ........................................................... 98

4.1.8 CS Voice over HSPA users allocation ................................. 99

4.1.9 HSUPA BTS Processing Set resources allocation ............ 100

5 Extended cell in Flexi BTS .............................................. 103

5.1 Extended cell dimensioning details .................................... 103

6 WCDMA BTS capacity allocation principles ................. 106

6.1 System Module rel.3 capacity details ................................. 106

6.2 System Module rel.2 capacity details ................................. 109

6.3 CCCH baseband resources allocation details ................... 110

6.4 CCCH baseband resources allocation for SM rel.3 details 112

6.5 CCCH baseband resources allocation for SM rel.2 details 115

6.6 Local Cell Grouping details ................................................ 115

6.7 Allocation of Dedicated Channels ...................................... 121

6.8 HSDPA allocation principles .............................................. 121

6.8.1 Fixed LCGs ........................................................................ 122

6.8.2 Flexible LCG. Maximum Throughput per HSDPA Scheduler commissioned on both System Modules .......... 122

6.8.3 Maximum Throughput per HSDPA Scheduler commissioned on one of the two System Modules ............ 124

6.8.4 Maximum Throughput per HSDPA Scheduler not commissioned on any of the two System Modules ............ 124

6.9 E-TFCI table selection........................................................ 125

7 Multi RAB .......................................................................... 126

7.1 HSDPA + AMR call resource allocation ............................. 126

7.2 HSUPA + AMR call resource allocation ............................. 127

7.3 HSUPA/HSDPA + HSUPA/HSDPA call resource allocation127

7.4 DCH + DCH call resource allocation .................................. 128

Summary of changes


5 (128)))



Summary of changes

The document comprises 128 pages.

Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Changes between issues 02C (2013-08-22, RU40) and 02D (2013-03-14, RU40)

New structure of the guideline

Chapter 2.7 - Information about LCG updated

Changes between issues 02B (2013-05-30, RU40) and 02C (2013-08-22, RU40)

Chapter 2.3 - 3 cells case and FSME System Module, BTS SW needs more BB capacity to handle high traffic scenario. Instead of 19 subunits there is 18 subunits available for 3 cells

Chapter 4 - Information about HSUPA resources allocation added

Changes between issues 02A (2013-03-01, RU40) and 02B (2013-05-30, RU40)

System Module rel.3 + System Module rel.2 configuration support removed.

Chapter 2.4 - Additional information regarding baseband allocation principles added.

Chapter 4 - Additional information regarding HSUPA baseband allocation added

HSUPA Dimensioning tables for SM Rel.3 update

Roadmap changes – Dual Band HSDPA feature removed from RU40 feature content

Dimensioning WCDMA RAN: Flexi BTS Baseband Introduction

DN0981084 Issue 02D


DND 6 (128)))

1 Introduction This dimensioning guideline is focused on Multiradio Flexi BTS WCDMA dimensioning in RU40 and Flexi Direct BTS Rel.5 release covering WBTS8.0 release.

Multiradio Flexi BTS WCDMA


7 (128)))



2 Multiradio Flexi BTS WCDMA A BTS type called Flexi WCDMA BTS has been available since RAS05.1. Multiradio Flexi BTS WCDMA is a new, truly modular, very compact, and high capacity wide-area WCDMA BTS that can be used in various indoor and outdoor installation options (such as floor, wall, stand, pole, mast, cabinet, 19" rack) and site applications (mini, macro, and distributed site solution).

This solution can also be used as a multimode upgrade to existing UltraSite EDGE BTS with WCDMA carriers.

Multiradio Flexi BTS WCDMA consists of the following self-supporting BTS modules:

Radio Module provides the Radio Frequency (RF) functionality. Maximum of three RF Modules can be directly connected to the Master System Module.

System Module provides baseband processing as well as control and transmission functionality;

System Module capacity depends on system module type, for details see section 2.2. The number of Rel99 CEs activated can be increased by license control;

The Baseband Extension Module is also available. In case of two system modules in one BTS, Flexi System Extension Kit cable set (FSKA) is required.

Dimensioning WCDMA RAN: Flexi BTS Baseband Multiradio Flexi BTS WCDMA

DN0981084 Issue 02D


DND 8 (128)))

RF module

RF module

RF module

Extension System

Module

BTS System Module

BBUAC > DCAC

(Optional)

RF module

RF module

RF module

Extension System

Module

BTS System Module

BBUAC > DCAC

(Optional)

Figure 1 Multiradio Flexi BTS WCDMA modules (Without Extended BTS Site capacity feature)

There are four kinds of RF Modules available, namely:

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 WCDMA BTS provides up to 18-cell capacity. Up to six sectors or up to eight carriers per configuration are supported by the hardware. The output power options of min 8/10/15/20/30/40W/60W or 80W (depending on the RF module) are available.

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

There are the following Flexi System Modules types available:

FSMB System Module (Rel.1 HW);

FSMC Flexi Multimode BTS System Module (Rel.2 HW);

FSMD Flexi Multimode BTS System Module (Rel.2 HW);

FSME Flexi Multimode BTS System Module (Rel.2 HW);



9 (128)))



FSMF Flexi Multiradio BTS 10 System Module (Rel.3 HW)

FBBA (Rel.3 HW) capacity extension submodule for FSMF System Module.

RU40 does not bring any changes for System Module Rel.1 (FSMB) baseband dimensioning rules therefore for more information related to BTS configurations including HW Rel.1 System Module please refer to RU30 baseband dimensioning guidelines

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

Flexi Rel.3 Multiradio System Module FSMF has 5.5 subunits.

Figure 2 FSMF System Module structure

In RU40 Multiradio 10 BTS consists of single System Module Rel.3 only.

Figure 3 System Module Rel.3 possible BTS configurations

System Module Rel.2 (FSMC/D/E) supports up to twelve (2-way Rx Div) cells or six (4-way Rx Div) cells. To support more than twelve (2-way Rx Div) / six (4-way Rx Div) cells per BTS, two System Modules Rel.2 and 18-Cells BTS (RAN2736) feature are needed (max 18 cells (2-way Rx Div) / 9 cells (4-way Rx Div)) per BTS are then supported.

Flexi Rel.2 Multimode System Module FSMC has five subunits. See Figure 3 for FSMC System Module Structure.


DN0981084 Issue 02D


DND 10 (128)))

Figure 4 FSMC System Module dimensioning structure

Flexi Rel.2 Multimode System Module FSMD has twelve subunits. See below figure.

Figure 5 FSMD System Module dimensioning structure

Flexi Rel.2 Multimode System Module FSME has nineteen subunits.

Figure 6 FSME System Module dimensioning structure



11 (128)))



2.1 Flexi BTS HW release mixed configurations

The table below presents Flexi BTS available combinations of Master and Extension System Module

Master System Module / Extension System Module

Extension System Module

System Module Rel.1 (FSMB)

System Module Rel.2 (FSMC/D/E)

System Module Rel.3

(FSMF)

Ma

ste

r S

ys

tem

Mo

du

le System Module

Rel.1 (FSMB) X X -

System Module Rel.2 (FSMC/D/E)

- X -

System Module Rel.3 (FSMF)

- * *

Table 1 Flexi BTS available configurations

where:

X – supported configuration

* - support foreseen in the future

2.2. 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


DN0981084 Issue 02D


DND 12 (128)))

The table below presents the number of subunits in System Module Rel.3 that can be used for R99/HSDPA/HSUPA traffic processing or additional CCCH and interference cancellation processing.

System Module Rel.3

Capacity Extension

Submodule

Number of subunits

FSMF - 5.5

FSMF FBBA 11.5

FSMF FBBA + FBBA 17.5

Table 2 Number of subunits inside System Module Rel.3

Note that System Module Rel.3 contains resources for Common Control Channels processing for basic configurations. For example, three cells with a cell range up to 20km, or six cells with a cell range up to 10km (2-way Rx diversity assumed).

One System Module Rel.3 subunit provides capacity of 96 Rel99 CE.

The maximum available baseband capacity of System Module Rel.3 for pure traffic depends on:

Local Cell Group (LCG) configuration type;

Additional CCCH processing resources (if needed);

Number of activated Interference Cancellation units (PIC pools);

HSUPA static resources (optional static reservation for HSUPA data/voice users)

HS_Cell_FACH_UL static resources (static reservation for HS-FACH UL users)

Local Cell Grouping allows splitting available baseband capacity into baseband pools responsible for processing traffic from dedicated group of cells.

Local Cell Grouping may be needed in case of BTSs with many cells, and can be used in Multi Operator RAN (MORAN). For more information related to Local Cell Grouping, see chapter 2.7.

There are three LCG configuration types available for System Module Rel.3 which describes HSPA capability (number of HSPA supported cells and number of HSDPA/HSUPA schedulers). The three LCG configuration types are as follow:



13 (128)))



Rel.99 only configuration

Small HSPA configuration

Normal HSPA configuration

The LCG configuration type is set during BTS commissioning for each LCG separately

using HSPA setting parameter. If not commissioned then Normal HSPA configuration

is assumed by default.

Figure 7 Exemplary BTS with 3 LCGs and different LCG configuration types

Table 3 presents LCG configuration type detail information related to number of supported HSPA cells/HSDPA schedulers amount.

LCG configuration

type

Max number of supported

cells

Max number of HSPA

cells

Number of HSDPA

schedulers

Rel.99 only 12 0 0

Small HSPA 6 6 1

Normal HSPA 12 12 2

Table 3 System Module Rel.3 LCG configuration type details

With Small HSPA and Normal HSPA configuration, HSDPA scheduler resources (HSDPA subunits) provides certain amount of CCCH baseband processing resources (so called


DN0981084 Issue 02D


DND 14 (128)))

CCCH pools) that can be used as additional CCCH processing resources. For more information, see chapter 2.5.1.

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

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

HSDPA scheduler processing subunits

Interference Cancellation units (PIC pools) subunits

HSUPA static allocation processing subunits.

Subunits for pure traffic capacity can be used for R99 (DCH) users, HSDPA users (A-DCH/SRB) and HSUPA users (HSUPA scheduler).

Figure 8 Exemplary picture presenting FSMF System Module, 1 LCG scenario with 12 HSPA (non-MIMO) cells and one interference cancelation (PIC pool) unit

The table below presents HSDPA schedulers and CCCH processing requirements for typical scenarios. Table assumes non-MIMO cells, 10km cell range and 2-way Rx Diversity. Note that the maximum 12 cells per BTS are supported.



15 (128)))



LCG configuration

Number of HSPA (non –

MIMO and non-VAM) cells per

LCG

1st

LCG [subunits]

2nd

and next LCG [subunits]

Rel99 only 0 (6 non-HSPA cells) 0 0,5 (CCCH)

Rel99 only 0 (12 non-HSPA cells) 0,5 (CCCH) 1 (CCCH)

Small Up to 6 cells 0,625 (HSDPA scheduler*)

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

scheduler*) = 1,125

Normal Up to 6 cells 1,125 (HSDPA scheduler*)

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

scheduler*) = 1,625

Normal 7 - 12 cells 1,125 (HSDPA scheduler*)

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

scheduler*) =1,625

- One CCCH Processing Set license required

- Two CCCH Processing Set licenses required

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

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

The table below presents HSDPA schedulers and CCCH processing requirements for typical scenarios. Table assumes MIMO cells, 10km cell range and 2-way Rx Diversity. Note that in maximum 12 cells per BTS are supported.


DN0981084 Issue 02D


DND 16 (128)))

LCG configuration

Number of HSPA (VAM

MIMO or VAM non-MIMO)

cells per LCG

1st

LCG [subunits]

2nd

and next LCG [subunits]

Rel99 only 0 (6 non-HSPA cells) 0 0,5 (CCCH)

Rel99 only 0 (12 non-HSPA cells) 0,5 (CCCH) 1 (CCCH)

Small Up to 4 cells 0,625 (HSDPA scheduler*)

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 (HSDPA scheduler*)

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

scheduler*) = 1,625

Normal 7 – 8 cells 1,625 (HSDPA scheduler*)

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

scheduler*) = 2,125


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

scheduler*) = 2,625


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 in HSDPA scheduler resources (CCCH Processing Set(s) required for activation)

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

All values in the tables above were calculated according to Equation 10 presented in chapter 6.1



17 (128)))



2.3. Flexi Multimode BTS system module capacity

The table below presents the number of subunits in System Module Rel.2 that can be used for R99/HSDPA/HSUPA traffic processing or additional CCCH and interference cancellation processing.

Number of cells FSMC FSMD FSME

1 – 2 5 12 19

3 5 12 18

4 – 6 4 11 18

7 – 9 2+1* 9+1* 16+1*

10 – 12 1+1* 8+1* 15+1*

Table 6 Number of subunits inside System Module Rel.2

* One subunit needed (1 CCCH Processing Set / 48 Rel99 CE (pure System Module Rel.2 BTS)) for CCCH processing (cell range up to 10km) with one System Module Rel.2. With two System Modules Rel.2, additional CCCH resources are not required (cell range up to 10km / 2-way Rx diversity assumed).

For example:

1) FSME + FSME / 1LCG 12 cells/10km; Number of subunits = 16 + 16 = 32 subunits available for traffic use (CCCH requirements are covered by resources included in the System Modules Rel.2 capacity);

2) FSME (LCG1 / 6cells/10km) + FSME (LCG2 – 6cells/10km) – 2LCGs 12 cells/10km; Number of subunits = 18 + 18 = 36 subunits available for traffic use (CCCH requirements are covered by resources included in the System Modules Rel.2 capacity).

Similar to previous releases, each System Module Rel.2 contains resources for Common Control Channels processing for basic configurations (for example, three cells with a cell range up to 20km, or six cells with a cell range up to 10km) included in the System Module capacity.

See Table 7 System Module Rel.2 capacity (HSDPA not activated) presenting the maximum System Module Rel.2 Rel99 CE capacity when HSDPA scheduler is not activated.


DN0981084 Issue 02D


DND 18 (128)))

Number of cells FSMC

(Rel99 CE)

FSMD

(Rel99 CE)

FSME

(Rel99 CE)

1 – 2 240 576 912

3 240 576 864

4 – 6 192 528 864

7 – 9 96 + 48* 432 + 48* 768 + 48*

10 – 12 48 + 48* 384 + 48* 720 + 48*

Table 7 System Module Rel.2 capacity (HSDPA not activated)

* One subunit needed for CCCH processing (cell range is up to 10km / 2 way Rx diversity) with one System Module Rel.2 (Extension System Module not available)



19 (128)))



2.4. Baseband allocation basics

Each LCG have own CCCH processing resources which are either included in System Module capacity or allocated at LCG baseband capacity. LCG CCCH processing resources might be located at Master System Module, Extension System Module or at both System Modules, depending where LCG HSPA resources are allocated. CCCH processing resources are allocated at the same System Module as HSDPA and HSUPA scheduler.

HSDPA and HSUPA scheduler is allocated in the same System Module. With baseband pooling (more than one LCG) or Frequency mapping to System Module (the operator can map frequency layers to different System Modules), it is possible to have HSPA on both System Modules. HSDPA scheduler in System Module rel.3 is LCG specific, which means that both HSUPA and HSDPA scheduler is allocated in the same LCG.

Note:

Dual Cell HSDPA /Dual Band HSDPA cells from the same sector need to be

served by one System Module and one scheduler, and belong to the same LCG

Figure 9 Exemplary BTS configuration with two System Modules rel.2, without Frequency mapping to HW and one LCG

Figure 10 Exemplary BTS configuration with two System Modules rel.2, with Frequency mapping to HW and one LCG


DN0981084 Issue 02D


DND 20 (128)))

The associated DCH (A-DCH) and HSDPA signaling resources (SRB) are allocated inside LCG capacity at the same System Module as HSDPA scheduler.

Figure 11 Exemplary BTS configuration with two System Modules rel.2, HSPA in Master System Module.

For more information about HSDPA resources allocation please see chapter 3

HSUPA scheduler can utilize LCG baseband capacity within one System Module only. With System Module Rel.3 single HSUPA scheduler can utilize FSMF System Module capacity including both extension submodules (FBBA).

For multi RAB calls see chapter 7.



21 (128)))



2.5. Common Control Channels

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

1 x P-SCH (Primary – Synchronization Channel);

1 x S-SCH (Secondary – Synchronization Channel);

1 x P-CCPCH (Primary – Common Control Physical Channel);

1 x P-CPICH (Primary – Common Pilot Channel);

1 x PICH (Paging Indicator Channel);

1 x AICH (Acquisition Indicator Channel);

3 x S-SCCPCH (Secondary Common Control Physical Channel).

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

The cells with ranges bigger than 20 km are called extended cells. Required baseband resources for Common Control Channels for extended cells are described separately in chapter 5 .

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

CCCH baseband processing resources are statically allocated in steps, so called CCCH pools. Each CCCH pool requires CCCH license - 48 Rel.99 CE (System Module Rel.2 BTS) or CCCH Processing Set license (System Module Rel.3).

With commissioning parameter Mapping HSPA Cell to HW, the operator can map frequency layers to different System Modules (at least one System Module Rel.2 is required). Some frequencies can be mapped to one System Module and other frequencies to another System Module.

If some frequency layer is mapped to a System Module, the selected System Module has to provide Common Control Channels, HSUPA, and HSDPA processing resources (including A-DCH and SRB resources) for cells from the assigned frequency layer. In this case, DCH users from the assigned frequency layer are also allocated at the selected System Module. However, when the full System Module capacity is occupied, new DCH users can be allocated at the second System Module.

Baseband resource allocation for CCCH processing can be influenced by ‘Frequency layer mapping to System Modules.


DN0981084 Issue 02D


DND 22 (128)))

2.5.1. CCCH requirements for Multiradio 10 BTS system modules

Similar to Rel.2 HW also System Module Rel.3 (FSMF) provides one CCCH pool included in System Module Rel.3 capacity which does not require any license.

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

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

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




2 * System Module: 12 cells/10 km (for example 4+4+4 with 10 km cells).

Listed above configuration assumes 2-way Rx Div enabled. If 4-way Rx Div feature is enabled then number of cells or cell range supported by free resources is halved.

In case when more cells or higher cell radius is needed additional baseband resources (CCCH pools) and CCCH Processing Set licenses need to be allocated for CCCH processing. One System Module Rel.3 CCCH pool corresponds to 0.5 subunits.

The HSDPA scheduler(s) resources (HSDPA subunits) provide certain amount of baseband resources (CCCH pools) that can be used for additional CCCH processing. It means that each LCG requires at least one CCCH pool (0.5 subunits) for CCCH processing unless CCCH processing is performed with resources included in SM Rel.3 baseband capacity. CCCH processing for remaining cells can be performed with baseband resources included in HSDPA scheduler capacity (HSDPA subunits). In order to utilize these resources for CCCH processing CCCH Processing Set licenses are required.

Below you can find a list of exemplary configurations and CCCH Processing Set licenses / CCCH subunits requirements for different LCG configuration types. Note that table is valid for first LCG only (second and next LCG might require additional 0.5 su for CCCH processing)



23 (128)))



LCG configuration

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

R99 Only

0 CCCH Processing

Sets /0 subunit

0 CCCH Processing

Sets /0 subunit

1 CCCH Processing Sets /0.5 subunit


2 CCCH Processing

Sets /1 subunit



Small HSPA

0 CCCH Processing

Sets /0 subunit

0 CCCH Processing

Sets /0 subunit

1 CCCH Processing

Set /0 subunit

- - - -

Normal HSPA (non-MIMO cells* assumed)

0 CCCH Processing

Sets /0 subunit

0 CCCH Processing

Sets /0 subunit

1 CCCH Processing

Sets /0 subunit

1 CCCH Processing

Set /0 subunit

2 CCCH Processing

Sets /0 subunit

1 CCCH Processing

Set /0 subunit


Normal HSPA (MIMO cells**

assumed)

0 CCCH Processing

Sets /0 subunit

0 CCCH Processing

Sets /0 subunit

1 CCCH Processing

Sets /0 subunit

1 CCCH Processing

Set /0 subunit

2 CCCH Processing

Set /0 subunit

1 CCCH Processing

Set /0 subunit

3 CCCH Processing

Set /0 subunit

*non-MIMO and non-VAM cells assumed

** MIMO or VAM non-MIMO cells assumed

Table 8 CCCH Processing Sets and subunits required for CCCH processing with System Module Rel.3 (2 way Rx Div assumed) and single LCG

Three additional CCCH Pools are available in HSDPA scheduler resources (HSDPA subunits). In order to utilize these resources for CCCH processing (as additional CCCH processing resource), CCCH Processing Set licenses are required.


DN0981084 Issue 02D


DND 24 (128)))

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

CCCH pools included in HSDPA scheduler(s) baseband resources can be used for additional CCCH processing (if needed e.g. extended cell range case or higher cells configuration). CCCH Processing Set license is needed for activation.

2.5.2. CCCH requirements for Multimode System Modules

Rel.2 HW System Modules (FSMC, FSMD, and FSME) provides one free CCCH pool (which does not require any license) available for Common Control Channels processing for basic configurations Below you can find a list of typical configurations covered by resources included in System Modules Rel.2 capacity.





2 * System Module: 12 cells/10 km (for example 4+4+4 with 10 km cells).



25 (128)))



Listed above configuration assumes two-way Rx Div enabled. If four-way Rx Div feature is used, then a number of cells or cell range supported by free resources will be halved.

In case when more cells or higher cell radius is needed, additional baseband resources (CCCH pools) and CCCH Processing Set licenses need to be allocated for CCCH processing. One System Module Rel.2 CCCH pool corresponds to one subunit.

Below are the exemplary configurations and CCCH resources (CCCH Processing Set license and amount of subunits) that may need to be licensed as follows:

Table 9 CCCH processing resources required for System Module Rel.2 BTS

NOTE:

Single cell cannot be split between two CCCH pools (subunits).

2.6. Capacity licenses

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

Flexi WCDMA BTS Baseband capacities are allocated according to the capacity license file. Because the ATM Cross-Connection (AXC) and the BTS exist in high volumes in the network, NSN does not generate licenses for these network elements directly (NE licenses), but so-called pool licenses are used. This means that the user gets the license to use a dedicated amount of features or capacity (pool license) and it is up to the user to determine how these NE licenses are distributed 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 this pool license and the help of the license management tools in NetAct, one can distribute the capacity

BTS configuration

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

1 x System Module Rel.2

(e.g. FSMD)

48 Rel.99 CE

48 Rel.99 CE

96 Rel.99 CE

48 Rel.99 CE 144 Rel.99

CE

2 x System Module Rel.2

(e.g. FSME + FSMD)

0 Rel.99 CE 0 Rel.99 CE 48 Rel.99

CE 0 Rel.99 CE 96 Rel.99 CE


DN0981084 Issue 02D


DND 26 (128)))

according to the capacity needs. For example: 120 Rel99 CE for BTS-1, 70 Rel99 CE for BTS-2, and so on. For this purpose, NetAct generates the appropriate license files and downloads them to the network elements.

There are four types of capacity licenses:

- CCCH Processing Set license o Applicable only for CCCH processing (may be required for high cell

configurations or extended cell range case) – (System Module Rel.3) - Rel99 CE license

o Applicable for Rel99 traffic (System Module rel.2 and System Module rel.3) and additional CCCH processing (System Module rel.2)

- HSDPA BTS Processing Set license o Applicable for HSDPA throughput and HSDPA users (System Module

Rel.2 and System Module Rel.3) - HSUPA BTS Processing Set license

o Applicable for HSUPA throughput and HSUPA users (System Module Rel.2 and System Module Rel.3)

System Module release

CCCH processing

Rel99 traffic HSDPA traffic HSUPA traffic

System Module Rel.2

(FSMC/D/E)

Rel99 CE license

Rel99 CE license

HSDPA BTS Processing Set license

HSUPA BTS Processing Set

license

System Module Rel.3 (FSMF)

CCCH Processing Set

license

Rel99 CE license

HSDPA BTS Processing Set license

HSUPA BTS Processing Set

license

Table 10 Baseband capacity licenses

In case of System Module Rel.2 and System Module Rel.3, the Rel99 CE license defines the maximum capacity for pure Rel99 traffic. HSDPA/HSUPA schedulers are not consuming Rel99 CE licenses.

The HSDPA BTS processing set describes the maximum HSDPA capability (System Module Rel.2 and System Module Rel.3) that allows reaching a certain number of HSDPA users and DL throughput.

Note that the HSDPA BTS processing set does not directly increase the capacity for maximum user amount and throughput. Separate ASW (application software) 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.

HSDPA BTS processing set throughputs and number of users are applicable for System Module Rel.2 and System Module Rel.3 HSDPA scheduler(s).



27 (128)))



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

The HSUPA BTS processing set describes the maximum HSUPA capability (System Module Rel.2 and System Module Rel.3) that allows reaching certain number of HSUPA users and UL throughput.

In RU40/Flexi Direct BTS Rel.5 the HSUPA BTS processing set provides simultaneously throughput (5.8Mbps) and user amount (24 HSUPA data/CS voice over HSPA users).

With x number of available HSUPA licenses, the HSUPA baseband reservation inside System Module Rel.2/System Module Rel.3 is able to fulfill the simultaneous x * 5.8Mbps and x * 24 users requirement. Note that there are more than 15 subunits, but maximum of 15 subunits (System Module Rel.2) / 16.875 subunits (System Module Rel.3) can be used for HSUPA.

Multi RAB UE having more than one HSUPA RAB is counted as one user from HSUPA Processing Set license point of view. For example 24 Multi RAB UEs, each having two HSUPA RABs, consume one HSUPA Processing Set license.

The SW uses the whole Rel99 CE capacity (from basic and extension System Module) up to the license capacity. There is no need to dedicate any Rel99 CE to Basic System Module and Extension Module.

For commissioning purposes, all licenses (including Rel99 CE licenses) are activated 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, while commissioned

numberOfR99ChannelElements is set to 900, then BTS shall only use 900

R99 CE licenses.

2.7. Local Cell Grouping for Flexi BTS

Local Cell Grouping may be needed in case of BTS sites with many cells, and can be used in Multi Operator RAN (MORAN) cases to divide baseband capacity to Local Cell Groups (LCGs). It is possible to use MORAN without Local Cell Grouping and dedicated baseband allocation.

A single LCG covers up to twelve cells with pure HW release 2 or HW release 3 configurations (System Module + RF module). However, when 4-way Rx diversity is used, up to six 4-way RX diversity cells can be dedicated to one LCG.

Local Cell Grouping for Flexi BTS is needed if more than six cells are configured per BTS with at least one release 1 HW (RF module) or if more than two cells are configured using Antenna 1 and Antenna 3 for cell from same Release1 dual radio module (see Figure 7). It is also possible to allocate baseband capacity for LCGs if the same site is divided between several operators (MORAN) who want to reserve some dedicated BB capacity for own use.


DN0981084 Issue 02D


DND 28 (128)))

Figure 14 Dual radio module, sector configuration type B

NOTE:

Small HSPA configuration (System Module Rel.3) supports up to 6 cells in single

LCG. If more cells in one LCG need to be supported, Normal configuration HSPA

(up to 12 HSPA + R99 cells) or R99 Only configuration (up to 12 R99 cells)

should be configured.

In Local Cell Grouping with 2 System Modules, some of the cells are dedicated to the Master System Module and some of the cells to the Extension System Module, depending on the HW that is used. See more information below and in the Flexi WCDMA BTS Commissioning Manual.

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

1) Flexible BB allocation / Fixed BB HW Rel.1 allocation;

2) Fixed BB allocation.

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

Option 1) Flexible BB allocation is applicable to pure Rel.2/Rel.3 BTS HW (System

Modules and RF Modules) and supports free adjustment of Access Baseband

Capacity parameter (visible in BTS Site Manager as ‘Max HW BB capacity’) for up

to four LCGs. Whole carriers can be mapped to LCGs or carriers can be split between LCGs freely (free mapping of cells to LCGs)

Option 1) Fixed BB HW Rel.1 allocation is applicable to Rel.1 BTS HW (System Module or RF Module). LCGs are based on whole System Module Capacity: one LCG per one System Module and up to two LCGs with two System Modules. Cells can be freely mapped to LCGs when both System Modules are Rel.2 while RF modules are Rel.1

Option 2) Fixed BB allocation is allowed with two System Modules Rel.2 and RF Modules Rel.2 / Rel.3. Two LCGs and two System Modules Rel.2 are mandatory. LCG capacity is based on System Module capacity: one LCG per one System Module and

Access Baseband Capacity parameter cannot be used. Cells can be freely mapped

to LCGs. Mapping of LCG to System Module is supported with sModId parameter – see

below example. Fixed BB allocation is required to support more than 12 cells with two System Modules Rel.2.



29 (128)))



Figure 15 Fixed BB allocation and exemplary LCG configurations

Flexible BB allocation / Fixed BB HW Rel.1 allocation

If at least one RF Module is Rel.1, the available baseband capacity is shared between LCGs according to the System Module capacity. Such LCGs are later referred as fixed LCGs (fixed baseband pools).

If both System Modules are Rel.2 or System Module Rel.3 is used (FSMC/FSMD/FSME/FSMF) while all RF Modules are Rel. 2 / Rel. 3 or Multi Carrier RRHs, the BB capacity can be freely dedicated among LCGs (operators) by defining in

commissioning the Access Baseband Capacity parameter. Such LCGs are later

referred as flexible LCGs (flexible baseband pools). The Access Baseband Capacity

commissioning parameter is used to divide the Baseband HW for LCGs from 1% to 99%. The actual allocation is done according to the rule: that at least one subunit is allocated to each LCG. The percentage division is rounded to one subunit.

In case of flexible LCGs, up to four LCGs can share the Baseband capacity.

In case of fixed LCGs, up to two LCGs can share the Baseband capacity.

Flexible BB allocation is required to support more than 12 cells with System Module Rel.3 (all RF modules must be Rel.2/Rel.3)

For more information related to LCG capacity allocation see chapter 6.6

2.8. Dedicated Channels

For baseband dimensioning purposes, a certain number of Rel99 CE per each active DCH user is required. Baseband resources are required per each DCH active user in “no handover” state and per each DCH user in “soft handover” state. Additional baseband


DN0981084 Issue 02D


DND 30 (128)))

resources are not required either for users in softer handover state or compressed mode. For multi RAB cases, Rel99 CE requirements need to be calculated as a sum of Rel99 CE requirements for single bearers used in multi RAB call.

The number of Rel99 CE depends on RB type and minimum SF. Table 11 presents required number of Rel99 CE per each active connection for basic set of RABs.

RAB Traffic class CS /PS

Max Rates for each

RAB, kbps

Min SF Required

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 11 Baseband resources required per one Rel99 traffic channel in RU40/Flexi Direct BTS Rel.5 (System Module Rel.2 and System Module Rel.3)



31 (128)))



2.8.1. Asymmetric UL/DL Rel99 CE allocation

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

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

Figure 16 Example of Rel99 CE allocation

Dimensioning WCDMA RAN: Flexi BTS Baseband HSDPA and BTS dimensioning

DN0981084 Issue 02D


DND 32 (128)))

3 HSDPA and BTS dimensioning Some supported capacities mentioned in this document may require separate licenses in the RAN before they can be activated. For more information, see Licenses Management in WCDMA RAN. For more specific information related to HSDPA, see HSDPA in BTS document.

3.1 Flexi System Module Rel.3 HSDPA scheduler

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 configuration type commissioning parameter. With Small HSDPA configuration one HSDPA scheduler is available while Normal HSPA configuration supports two HSDPA schedulers.

HSPA Configuration Number of HSDPA

schedulers Max number of

supported HSPA cells

Rel99 Only 0 0

Small HSPA 1 6

Normal HSPA 2 12

Table 12 LCG configuration types for System Module Rel.3

HSDPA scheduler based on System Module Rel.3 is LCG specific – it supports only cells dedicated to LCG. In comparison to System Module Rel.2, it does not require any additional baseband resources to reach high HSDPA throughput. In other words, it provides HSDPA throughput up to 252Mbps without commissioning any additional baseband resources for scheduler purpose.

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

The operator can specify the maximum throughput per each HSDPA scheduler. The maximum throughput for the scheduler is commissioned in steps called HSDPA

throughput steps (HSDPA Throughput Step). For each scheduler, the operator can

HSDPA and BTS dimensioning


33 (128)))



select HSDPA throughput step values from 1 up to 35. The HSDPA throughput step has no impact on HSDPA baseband capacity allocation but it is used for HSDPA licensed throughput distribution among available schedulers (for more information, see chapter 3.4). In addition it can be used to limit HSDPA scheduler throughput. Each HSDPA throughput step corresponds to 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 of active users per

HSDPA scheduler


cell

Max number of cells assigned to

HSDPA scheduler

Max scheduler

throughput

240 128 6 252 Mbps

Table 13 System Module Rel.3 HSDPA scheduler details

HS-Cell_FACH user is treated as normal HSDPA user with respect to maximum number of users supported by HSDPA schedulers. HS-Cell_FACH user does not require any CE resources for SRB purpose.

One HSDPA scheduler has 240 scheduling units. HSDPA user consumes following amount of scheduling units:

- One HSDPA user or one DC-HSDPA or one MIMO user consumes one scheduling subunit;

- One DC-HSDPA + MIMO user consumes 1.25 scheduling unit.

Thus, one HSDPA scheduler supports up to 240 (DC or MIMO or legacy) or 192 (DC + MIMO) HSDPA active users or a mixture of those from one to six cells.

For example:

100 HSDPA active users and 50 DC+MIMO users consume Round_up (100*1+50*1.25) = Round_up (100+62.5) = 163 scheduling units.


DN0981084 Issue 02D


DND 34 (128)))

Thus, additionally 240-163 = 77 scheduling units are unused allowing for allocation of additional 77 HSDPA or MIMO users or Round_down (77/1.25) = 61 DC+MIMO users.

Note that in two System Modules case the associated DCH (A-DCH) and HSDPA signaling resources are allocated inside LCG capacity at the same System Module as HSDPA scheduler.

3.2 Flexi System Module Rel.2 HSDPA scheduler

Only one type of HSDPA scheduler is available with System Module Rel.2. The scheduler provides high throughput, which depends on activated features, number and type of BTS processing sets, and HSDPA throughput commissioning by the operator. The System Module Rel.2 HSDPA scheduler does not consume any Rel99 CE licenses, but the desired number of active users and peak rate, is possible only with the appropriate number and type of HSDPA BTS processing sets.

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

There can be up to two HSDPA schedulers per system module. The number of enabled HSDPA schedulers depends on used TCELL groups. For more information about Tcell

grouping, see chapter 3.3.

The operator can specify the maximum throughput per each HSDPA scheduler. The maximum throughput for the scheduler is commissioned in steps called “HSDPA

throughput steps” (HSDPA Throughput Step). For each scheduler the operator can

select HSDPA throughput step values from 0 up to 35. The HSDPA throughput step has impact on HSDPA baseband capacity allocation (see Table 13 and Table 15) as well as parameter is used for HSDPA licensed throughput distribution among available schedulers (for more information, see chapter 3.4). Parameter commissioning is optional. However, if the throughput value is commissioned for one scheduler, then it has to be commissioned also to another scheduler in the same System Module. If the maximum throughput for HSDPA scheduler is set to 0, then the HSDPA scheduler is not available in a given System Module. Each HSDPA throughput step refers to 7.2Mbps. This means that operator can limit the HSDPA scheduler throughput according to the number of commissioned HSDPA throughput steps.

When there are two System Modules Rel.2 and more than one LCG or HSPA frequency layer mapping is used to different System Modules, then throughput can be commissioned to one or two schedulers on both System Modules resulting in maximum four HSDPA schedulers per BTS.

In case of two System Modules Rel.2, one LCG and HSPA frequency layer mapping is not used, HSDPA schedulers can be activated only at one System Module allowing for maximally two HSDPA schedulers per BTS.

Table 13 presents HSDPA throughput steps and the corresponding maximum HSDPA throughput for the HSDPA scheduler.



35 (128)))



HSDPA throughput steps

Maximum throughput for

HSDPA scheduler

0 0 Mbps

1, 2, 3, 4, 5, 6 42 Mbps

7, 8, 9, 10, 11, 12 84 Mbps

13, 14, 15, 16, 17, 18 126 Mbps

19, 20, 21, 22, 23, 24 168 Mbps

25, 26, 27, 28, 29, 30 210 Mbps

31,32, 33, 34, 35 252 Mbps

Table 14 System Module Rel.2 HSDPA throughput steps

NOTE:

HSPDA throughput commissioning is optional and is used only when

upgrade is not done using the NSN upgrade script. If HSDPA throughput

was not commissioned, and the user script (presenting SW upgrade

conversion settings) is not available, the default rule will be automatically

used for HSDPA cells as presented in Table 14.

HSDPA BaseBand resource allocation before SW update

(for example RU10, RU20)

Allocated throughput for HSPA cells (RU40)

Shared scheduler for BB efficiency 42 Mbps allocated to every two non-MIMO

cells or two MIMO cells

Full BaseBand 42 Mbps allocated to every two non-MIMO

cells or one MIMO cell

Minimum BaseBand Allocation 2*42 Mbps allocated to every 1-6 non-MIMO

cells or 1-3 MIMO cells

HSDPA 16 Users per cell 2*42 Mbps allocated to every 1-6 non-MIMO


Configuration not available 2*42 Mbps allocated to every 1-6 non-MIMO


Table 15 Default rule for HSDPA baseband capacity allocation


DN0981084 Issue 02D


DND 36 (128)))

HSDPA throughput allocation means baseband resource allocation for HSDPA processing. The achieved HSDPA throughput depends also on the available HSDPA processing set licenses and features which are activated (for example, HSDPA 64QAM or Iub configuration).

The HSDPA scheduler does not consume Rel99 CE licenses, but depending on commissioned HSDPA throughput, it reduces available baseband capacity. The table below presents the 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 (subunits for HSDPA throughput)

0 Mbps HSDPA schedulers not activated

42 Mbps 2

84 Mbps 2

126 Mbps 3

168 Mbps 3

210 Mbps 4

252 Mbps 4

294 Mbps 5

336 Mbps 5

378 Mbps 6

420 Mbps 6

462 Mbps 7

504 Mbps 7

Table 16 Maximum HSDPA throughput for System Module Rel.2

If HSDPA throughput, step value 0 was commissioned to both HSDPA schedulers in the same System Module (0 Mbps – HSDPA schedulers not activated), HSDPA is not activated at a given System Module and does not consume any baseband capacity.

HSDPA_scheduler_throughput =

Min {HSDPA_throughput_step * 7.2 Mbps ; Maximum throughput for HSDPA scheduler}

Equation 1 HSDPA baseband capacity allocation



37 (128)))



where:

HSDPA_throughput_step = commissioned scheduler throughput Maximum throughput for HSDPA = maximum throughput referred in Mbps for corresponding HSDPA throughput step from Table 13

For example:

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 =

Min {2 * 7.2Mbps; 42Mbps} = Min {14.4Mbps ; 42Mbps} = 14.4Mbps;

HSDPA_scheduler #2_throughput =

Min {6 * 7.2Mbps; 42Mbps} = Min {43.2Mbps ; 42Mbps} = 42Mbps.

Note that the HSDPA scheduler throughput can be limited with the HSDPA BTS processing set license(s). Baseband capacity 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

Equation 2 HSDPA baseband capacity allocation

where:

Subunits_for_HSDPA_throughput = number of subunits from Table 15;

Number_of_LCGs = number of LCGs using HSDPA resources that are located at System Module Rel.2. In case HSPA frequency layer mapping to HW is used, 0.25 is applicable to both System Modules Rel.2 (See below Example 2)

For example:

two HSDPA schedulers were activated at System Module Rel.2 with 1 LCG (6 non-MIMO cells and 3 MIMO cells), the maximum HSDPA throughput commissioned for schedulers is:

1st HSDPA scheduler 84Mbps (six non-MIMO cells);

2nd

HSDPA scheduler 42Mbps (three MIMO cells).

The total HSDPA throughput available per System Module is:

126Mbps = (84Mbps + 42Mbps);

To fulfill the HSDPA throughput conditions, three subunits required by HSDPA throughput have to be allocated (see Table 15).

According to Equation 2, HSDPA baseband capacity is:


DN0981084 Issue 02D


DND 38 (128)))

Subunits_for_HSDPA = Max {Round up ((2 * 3 (MIMO cells) + 6 (non-MIMO cells)) / 6) + 1 ; 3 } + 1 (number of LCGs) * 0.25 = Max {2 + 1 ; 3} + 0.25 = Max {3 ; 3} + 0.25 = 3 + 0.25 = 3.25 subunits;

Equation 2 provides the final number of subunits required for HSDPA. Therefore, in current example, 3.25 subunits are required for HSDPA.

One HSDPA scheduler has 240 scheduling units. HSDPA user consumes following amount of scheduling units:

- One HSDPA user or one DC-HSDPA or one MIMO user consumes one scheduling unit;

- One DC-HSDPA + MIMO user consumes 1.25 scheduling unit.

- One HS-FACH user consumes one scheduling unit

Thus, one HSDPA scheduler supports up to 240 (DC or MIMO or legacy) or 192 (DC + MIMO) HSDPA active users or a mixture of those from one to six cells.

One scheduler can support cell from different LCGs (covering BB capacity from System Module with activated HSDPA scheduler).


HSDPA scheduler


cell

Max number of cells assign to

HSDPA scheduler

Max scheduler

throughput

240

(192 DC-HSDPA + MIMO users)

128 6 252 Mbps

Table 17 System Module Rel.2 HSDPA scheduler details

Note that the associated DCH (A-DCH) and HSDPA signaling resources are allocated together with the HSDPA scheduler at the same System Module Rel.2. Single HSDPA scheduler supports 240 Radio Bearers. For example, in case of Multi RAB UE with ongoing HSDPA data download and simultaneous HSDPA web browsing, one scheduler can support 238 single RAB users in addition to one Multi RAB user with two HSDPA RABs.

For more information related to HSDPA scheduler resources allocation for System Module rel.2 BTS see chapter 6.8



39 (128)))



3.3 Tcell grouping with System Module Rel.2 and System Module Rel.3

Tcell grouping is used to group cells to the scheduler based on System Module Rel.2 and System Module Rel.3. Tcell groups 1 and 3 are handled by the first scheduler and Tcell groups two and four are handled by the second scheduler.

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

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

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

Group 1: Tcell values 0, 1 and 2;



Group 4: Tcell value 9.

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

Figure 17 System Module Rel.2/Rel.3 (1LCG) exemplary Tcell configurations (2/2)


DN0981084 Issue 02D


DND 40 (128)))

3.4 HSDPA BTS Processing Set resources allocation

HSDPA schedulers based on System Module Rel.3 require HSDPA license so called HSDPA BTS processing set. To learn more about HSDPA BTS processing sets, see chapter 2.6.

HSDPA license resources (specified by HSDPA BTS processing sets) are distributed among HSDPA schedulers/LCGs according to the rules presented below.

1) HSDPA throughput:

Total HSDPA licensed throughput is distributed among the available HSDPA schedulers.

When the maximum licensed HSDPA throughput per scheduler is calculated, it is divided between HSDPA schedulers proportionally to "Maximum Throughput per HSDPA”

commissioned values (HSDPA Throughput Step). ”Maximum Throughput per

HSDPA scheduler" is commissioned for each HSDPA scheduler separately. The commissioned step is 7.2Mbps.

If there are only HSDPA Processing Set 1 licenses present in BTS, the division 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 3 Scheduler licensed throughput with BTS Processing Set 1 type only

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

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

Equation 4 Scheduler licensed throughput with BTS Processing Set 2 or Set3 type

where:

Scheduler_licensed_throughput – licensed throughput available for given scheduler;

Number_of_HSDPA_Processing_Sets_2 – number of HSDPA Processing Sets 2 present in BTS;

Number_of_HSDPA_Processing_Sets_3 – number of HSDPA Processing Sets 3 present in BTS;



41 (128)))



Scheduler_HSDPA_throughput_step – HSDPA throughput step commissioned for given scheduler (see chapter 3.1 and 3.2);

Total_number_of_HSDPA_throughput_step_per_BTS – sum of all commissioned HSDPA throughput steps in the BTS.

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

a) Scheduler with lowest value of licensed throughput divided by commissioned throughput;

b) Schedulers belonging to LCG with the lowest ID ( in case of Normal HSPA configuration (2 HSDPA schedulers activated) scheduler#1 is prioritized over scheduler#2)

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

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

For example:

BTS configuration with two HSDPA schedulers (e.g. Normal HSPA configuration) and four HSDPA Processing Sets:

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

BTS has two HSDPA schedulers activated with following commissioned throughput:

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

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

According to Equation 4 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 is 147Mbps, while total scheduler licensed throughput is 21Mbps + 105Mbps = 126Mbps, thus remaining 21Mbps is distributed to schedulers 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 commissioned throughput = 21Mbps / 42Mbps = 0.5

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


DN0981084 Issue 02D


DND 42 (128)))

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

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

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

For example:

In case when only one HSDPA processing set 1 or set 2 was purchased, then the entire licensed throughput will be assigned to one scheduler (there is no more licensed throughput left for remaining schedulers).

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

In case when there are not sufficient HSDPA licenses compared to the number of scheduler, not all schedulers may get HSDPA throughput.

For example:

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

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 divided between LCGs according to the commissioned shares.

The operator has the possibility to select the dedicated HSDPA option during BTS

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%, then the remaining part is common and all LCG can utilize those licenses on a need basis.

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

For example:

If one HSDPA BTS processing set 3 license was bought, the available user amount is 72 users. If one LCG is set, all numbers of users can be taken.

If one HSDPA BTS processing set three licenses were bought and two LCGs were configured, the operator can commission, for example, 20% of all available users to LCG1 and 40% to LCG2. This means that the remaining 40% is common for both LCGs and can be shared freely between them.

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

For more information on HSDPA BTS processing set capacities, see chapter 2.6.



43 (128)))



3.5 Associated UL/DL DCH

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

User data Rel99 CE required

in UL / Min SF Rel99 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**

PS 384 kbps 8/SF4 1/SF128**

Table 18 Associated DCH and Rel99 CE usage

* If SF is 32, 2 Rel99 CE are required in UL;

** 1 Rel99 CE for DL signaling is required per HSDPA user;

Dimensioning WCDMA RAN: Flexi BTS Baseband HSUPA and BTS dimensioning

DN0981084 Issue 02D


DND 44 (128)))

4 HSUPA and BTS dimensioning Some supported capacities mentioned in this document may require separate licenses in the RAN before they can be activated. For more information, see Licenses 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 baseband capacity allocation may be changed dynamically between DCH and HSUPA use. In the baseband allocation, DCH has a higher priority than HSUPA. The operator may commission a minimum fixed reservation for HSUPA, but the rest of 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.2 one HSUPA scheduler can support up to 240 HSUPA users from one to twelve cells.

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 configuration Normal HSPA configuration

Max number of HSPA cells 6 12

Number of HSDPA schedulers:

1 2

Max number of HSDPA users

240 480

Number of HSUPA schedulers

1 1

Max number of HSUPA users

160 240

Table 19 Flexi System Module Rel.3 HSPA LCG properties

HSUPA and BTS dimensioning


45 (128)))



In WN8.0 only one HSUPA scheduler can be allocated per LCG, unless two System Modules are available and frequency mapping to both System Modules is used. In this case, up to two HSUPA schedulers can be allocated per one LCG (first HSUPA scheduler located at the first System Module and the second HSUPA scheduler allocated at another System Module).

Figure 18 Exemplary BTS configuration with Frequency mapping to HW

Therefore, with some configurations, more than one carrier and two Flexi System

Modules Rel.2 (for example FSME + FSME) – Mapping HSPA Cell to HW

commissioning parameter enables to achieve up to 480 HSUPA users per one LCG (two HSUPA schedulers - mapping frequency layers to both System Module used).

The Mapping HSPA Cell to HW commissioning parameter can be used by the

operator to map HSPA frequencies to different System Modules. Some frequencies can be mapped to one System Module and other frequencies to another System Module, so that both modules are utilized for HSPA.

Max number of HSUPA users FSMC/D/E

Max number of HSUPA users per Cell 128

Max number of HSUPA users per LCG 240(480*)

Table 20 Maximum number of HSUPA users per Cell/LCG

*- Frequency mapping to HW used (2 System Modules available)

The minimum HSUPA baseband allocation is 0 subunits. In this case, only HSUPA MAC-e is active.


DN0981084 Issue 02D


DND 46 (128)))

4.1 HSUPA users baseband allocation principles

4.1.1 HSUPA resource steps

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

HSUPA activation does not require fixed processing resources when the feature is being activated. For System Module Rel.2 and System Module Rel.3, at least one HSUPA BTS processing set and HSDPA BTS processing set is required.

To allocate the next HSUPA resource step, an additional free capacity of:

14 Rel99 CE is needed for System Module rel.2

6 Rel99 CE for System Module rel.3.

These 14 / 6 Rel99 CE are licensed Rel99 CE in each System Module where HSUPA scheduler is located (same LCG capacity). The required 14 / 6 Rel99 CE free on top of the HSUPA resource step is to avoid a “ping-pong” effect in reserving and freeing HSUPA resource steps. This is needed so that the HSUPA resource step is not requested back immediately after its allocation.

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

4.1.2 HSUPA resource allocation

HSUPA does not consume Rel99 CE licenses (even for SRB purpose). The maximum baseband resources that can be allocated for HSUPA are defined 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 NRT HSUPA users). HSUPA baseband resource allocation is performed on a step basis. One HSUPA baseband resource is called a HSUPA resource step.

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

System Module release System Module Rel.2

subunit System Module Rel.3

subunit

HSUPA resource step baseband capacity

0.25 subunit 0.125 subunit

Table 21 HSUPA resource step baseband capacity



47 (128)))



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

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

Figure 19 Example of baseband capacity reservation without license overlapping

See Figure 20 for an example of System Module Rel.2 baseband capacity reservation with license overlapping.


DN0981084 Issue 02D


DND 48 (128)))

Figure 20 Example of baseband capacity reservation with license overlapping

For overlapping R99 CE licenses and licensed HSUPA resources (defined by the number of available HSUPA BTS processing sets), commissioning can be performed in order to guarantee resources for HSUPA. HSUPA resource commissioning is 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 HSUPA resource steps belonging to one HSUPA scheduler is located inside the same System Module (HSUPA scheduler can utilize baseband capacity within one System Module only). This means that with System Module Rel.3, single HSUPA scheduler can utilize also both extension submodules capacity (FBBA).

4.1.3 Hybrid Processing Set

One HSUPA BTS Processing Set per each LCG (called hybrid HSUPA Processing Set) provides capacity of 48 Rel99 CE that can be used when all Rel99 CE licenses have been consumed. Each utilized Rel99 CE decreases amount of HSUPA users allowed by hybrid HSUPA Processing Set according to formula below:

Amount_of_allowed_HSUPA_users_by_hybrid_HSUPA_Processing_Set = 24 – Roundup (Amount_of_allocated_Rel99_CE / 2)

Equation 5 Amount of allowed by hybrid HSUPA Processing Set HSUPA users



49 (128)))



Where:

Amount_of_allowed_HSUPA_users_by_hybrid_HSUPA_Processing_Set – amount of HSUPA users allowed by hybrid HSUPA BTS Processing Set license

Amount_of_allocated_Rel99_CE – amount of Rel.99 CE allocated for R99 users from hybrid HSUPA Processing Set license capacity.

For example:

1 HSUPA BTS Processing Set license available

30 Rel99 CE licenses available

35 AMR 12.2 users exists in the BTS

30 AMR users consumes 30 Rel99 CE licenses while remaining 5 users consumes Rel99 CE capacity (5 Rel99 CE) from hybrid HSUPA Processing Set license

Amount_of_allowed_HSUPA_users_by_hybrid_HSUPA_Processing_Set = 24 – Roundup (Amount_of_allocated_Rel99_CE / 2) = 24 – Roundup (5 /2) = 24 – Roundup (2.5) = 24 – 3 = 21

21 HSUPA users are still allowed by hybrid HSUPA Processing Set license

When R99 users consume hybrid HSUPA license capacity also HSUPA throughput might be affected since less HSUPA resource step(s) are available for HSUPA scheduler. Hybrid HSUPA Processing Set license corresponds to:

8 hybrid HSUPA resource steps (System Module rel.3)

12 hybrid HSUPA resource steps (System Module rel.2).

The amount of hybrid HSUPA resource steps available for HSUPA scheduler depends on amount of utilized hybrid Rel99 CE according to formula below:

Amount_of_hybrid_HSUPA_resource_steps_for_HSUPA_purpose =

8 – Roundup(Amount_of_allocated_Rel99_CE / 6)

Equation 6 Amount of available hybrid HSUPA resource steps for System Module rel.3


12 – Roundup(Amount_of_allocated_Rel99_CE / 4)

Equation 7 Amount of available hybrid HSUPA resource steps for System Module rel.2

where:


DN0981084 Issue 02D


DND 50 (128)))

Amount_of_hybrid_HSUPA_resource_steps_for_HSUPA_purpose – amount of hybrid HSUPA resource steps available for HSUPA scheduler allocation.

Amount_of_allocated_Rel99_CE – amount of Rel.99 CE allocated for R99 users from hybrid HSUPA Processing Set license capacity.

When baseband capacity is covered by hybrid HSUPA Processing Set license and Rel99 CE licenses (license overlapping), formulas above take into consideration only not overlapped Rel99 CE (allocated Rel.99 CE available with hybrid HSUPA Processing Set license capacity).

For example:

FSMF System Module

One HSUPA BTS Processing Set available (8 hybrid HSUPA resource steps)

108 Rel.99 CE licenses available

2 hybrid HSUPA resource steps overlapped with Rel99 CE licenses

In total R99 traffic might consume 108 Rel99 CE (108 Rel.99 CE licenses) + 48 Rel.99 CE available with hybrid HSUPA Processing Set license.

120 AMR 12.2 users are in the BTS, which means that 120 Rel.99 CE are consumed (108 Rel99 CE licenses + 12 Rel99 CE from hybrid HSUPA Processing Set license)

Amount_of_allowed_HSUPA_users_by_hybrid_HSUPA_Processing_Set = 24 – Roundup (Amount_of_allocated_Rel99_CE / 2) = 24 – Roundup (12 / 2) = 24 – Roundup (6) = 24 – 6 = 18


8 – Roundup(12 / 6) = 8 – 2 = 6

After allocation of 12 Rel99 CE, hybrid HSUPA Processing Set license has capacity of 18 HSUPA users and 6 HSUPA resource steps are still available for HSUPA scheduler.



51 (128)))



Figure 21 Example scenario: hybrid HSUPA resource steps and Rel99 CE license overlapping (System Module Rel.3)

Note that hybrid HSUPA Processing Set is always dynamic and cannot be statically reserved

4.1.4 HSUPA Resource utilization – dimensioning approach

In order to dimension the HSUPA resource utilization the HSUPA dimensioning tables are used. Table 22, Table 23, Table 24, Table 25, Table 26 , Table 27, Table 28 and Table 29 presents HSUPA subunits utilization with the assumption that HSUPA 16QAM is not used, HSUPA licensed capacity is limited. Tables also assume scenario when the typical 50% of the users are DL data dominated and the remaining users are UL data dominated (E-DCH users actively uploading data). DL dominated user has a reservation in HSUPA BTS scheduler which is an equivalent of following baseband minimum decoding capabilities, depending on current UE TTI selection:

- 10ms TTI: 37.2 kbps

- 2ms TTI: 47.5 kbps

Moreover tables below assume:

Cell load is available. If cell load is a constraint then throughput will be lower

- Air or IuB interface can limit actually achieved end to end throughputs


DN0981084 Issue 02D


DND 52 (128)))

- The actual throughput achieved may be ~10% lower than the numbers defined in the table due to HSUPA BLER target



53 (128)))



HSUPA data UEs

per HSUPA scheduler

Baseband minimum decoding capacity [Mbps]

<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 20.3 21.7 23.2 24.6 26.1 27.5 29

1 0.25 0.5 0.75 0.75 0.75 N/A N/A N/A N/A 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 0.25 0.5 0.75 0.75 0.75 1.75 1.75 1.75 1.75 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 0.25 0.5 0.75 0.75 1 1.75 1.75 1.75 1.75 2 2 2.5 2.5 3 3 3 3.75 N/A N/A N/A N/A

5~6 0.25 0.75 1 1.75 1.75 1.75 1.75 1.75 2 2 2.5 2.5 2.5 3 3 3 3.75 4 4.5 4.5 5

7~8 0.25 0.75 1 1.75 1.75 1.75 1.75 1.75 2 2 2.5 2.5 2.5 3 3 3.25 3.75 4 4.5 4.5 5

9~10 0.25 0.75 1 1.75 1.75 1.75 1.75 1.75 2 2.75 2.75 2.75 3 3 3 3.25 3.75 4 4.5 4.5 5

11~12 0.5 0.75 1.75 1.75 1.75 1.75 2 2 2.5 2.75 2.75 2.75 3.25 3.25 3.25 3.25 4 4 4.5 4.5 5

13~14 0.5 0.75 1.75 1.75 1.75 1.75 2.5 2.5 2.5 2.75 2.75 2.75 3.25 3.25 3.25 3.25 4 4 4.5 4.5 5

15~16 0.5 0.75 1.75 1.75 1.75 2 2.5 2.5 2.75 2.75 2.75 3.25 3.25 3.25 3.25 3.25 4 4 4.5 4.5 5

17~18 0.5 0.75 1.75 1.75 1.75 2.5 2.5 2.5 2.75 2.75 3.25 3.25 3.25 3.75 3.75 4 4.75 4.75 4.75 5 5

19~20 0.5 0.75 1.75 2.25 2.25 2.5 2.5 2.5 2.75 2.75 3.25 3.25 3.25 3.75 4 4 4.75 4.75 4.75 5 5

21~22 0.75 0.75 1.75 2.25 2.25 2.5 2.5 2.75 3 3.25 3.25 3.25 3.25 3.75 4 4 4.75 4.75 4.75 5.25 5.25

23~24 0.75 0.75 1.75 2.25 2.5 2.5 2.75 3 3 3.25 3.25 3.25 3.25 3.75 4 4 4.75 4.75 4.75 5.25 5.25

25~26 0.75 0.75 1.75 2.25 2.5 2.75 3 3 3 3.25 3.25 3.25 3.25 4 4 4 4.75 4.75 4.75 5.25 5.25

27~28 0.75 1 1.75 2.25 2.5 2.75 3 3 3 3.25 3.25 3.25 4 4 4.75 4.75 4.75 4.75 4.75 5.25 5.25

29~30 0.75 1 1.75 2.25 2.5 2.75 3 3 3.5 3.5 4 4 4 4 4.75 4.75 4.75 4.75 5.25 5.25 5.75

31~32 1 1 1.75 2.25 2.75 3 3 3 3.5 3.5 4 4 4 4 4.75 4.75 4.75 5.25 5.25 5.25 5.75

33~34 1 1 1.75 2.25 2.75 3 3 3 3.5 3.5 4 4 4 4.75 4.75 4.75 4.75 5.25 5.25 5.25 5.75

35~36 1 1 1.75 2.25 2.75 3 3.25 3.25 3.75 3.75 4 4 4.75 4.75 4.75 4.75 4.75 5.75 5.75 5.75 6.25

37~38 1 1 1.75 2.25 2.75 3 3.25 3.75 3.75 3.75 4 4 4.75 4.75 4.75 4.75 4.75 5.75 5.75 5.75 6.25

39~40 1 1 1.75 2.25 2.75 3 3.25 3.75 3.75 3.75 4 4 4.75 4.75 4.75 5 5 5.75 5.75 5.75 6.25

Table 22 HSUPA resource allocation in number of subunits for System Module Rel.2 (F-DPCH 2ms TTI users)


DN0981084 Issue 02D


DND 54 (128)))

Table 22 HSUPA resource allocation in number of subunits for System Module Rel.2 (F-DPCH 2ms TTI users) - cont.

HSUPA data 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 20.3 21.7 23.2 24.6 26.1 27.5 29

41~44 1.25 1.5 1.75 2.25 2.75 3 3.25 3.75 3.75 3.75 4 4 4.75 4.75 4.75 5 5 5.75 5.75 5.75 6.25

45~48 1.25 1.5 1.75 2.25 2.75 3 3.25 3.75 3.75 3.75 4 4 4.75 4.75 4.75 5 5 5.75 5.75 5.75 6.25

49~52 1.5 1.75 2 2.25 2.75 3 3.25 3.75 3.75 3.75 4 4 4.75 4.75 4.75 5 5 5.75 5.75 5.75 6.25

53~56 1.5 1.75 2 2.25 2.75 3 3.5 3.75 3.75 3.75 4 4 4.75 4.75 4.75 5 5 5.75 5.75 5.75 6.25

57~60 1.5 1.75 2 2.25 2.75 3 3.5 3.75 3.75 3.75 4 4 4.75 4.75 4.75 5 5 5.75 5.75 5.75 6.25

61~64 1.75 1.75 2 2.25 3 3 3.5 4 4 4 4 4.5 5 5 5.5 5.5 5.5 5.75 5.75 5.75 6.25

65~68 1.75 1.75 2 3 3 3.5 3.5 4 4 4.5 4.5 4.5 5 5 5.5 5.5 5.5 5.75 5.75 5.75 6.25

69~72 2 2 2 3 3 3.5 3.5 4 4.5 4.5 4.5 4.5 5 5 5.5 5.5 5.5 6 6 6.25 6.25

73~76 2 2 2 3 3 3.5 4 4 4.5 4.5 4.5 4.5 5 5 5.5 5.5 5.5 6 6 6.25 6.75

77~80 2 2 2 3 3 3.5 4 4 4.5 4.5 5 5 5.5 5.5 6 6 6 6 6.75 6.75 6.75

81~100 2.5 2.5 3 3 3 3.5 4 4 5 5 5.5 5.5 6 6 6 6.75 6.75 6.75 6.75 6.75 6.75

101~120 3 3 3 3 3.5 4 5 5 5 6 6 6 6 6 6.5 6.75 6.75 7 7 7 7.75

121~160 4 4 4 4 4 4 5 5.5 6 6 6.5 7 7 7 7 7.5 7.5 8 8 8 8

161~200 5 5 5 5 5 5 5 6 6 7 7 7 8 8 8 8 9 9 9 9 9

201~240 6 6 6 6 6 6 6 6 7 7 8 8 8 9 9 9 9 9 10 10 10



55 (128)))




HSUPA data UEs

per HSUPA scheduler


30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9 46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58

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 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 N/A N/A N/A N/A N/A N/A N/A N/A

5~6 5 5.5 5.75 5.75 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

7~8 5 5.5 5.75 5.75 6 6 6.5 7 7 7 7.75 7.75 N/A N/A N/A N/A N/A N/A N/A N/A

9~10 5.5 5.5 5.75 6 6.5 6.5 6.5 7 7 7.5 7.75 7.75 8 8 8 9 9 9 9.75 9.75

11~12 5.5 5.5 6 6 6.5 6.5 6.5 7 7 7.5 7.75 8 8 8 8 9 9 9.5 10 10

13~14 5.5 5.5 6 6 6.5 6.5 6.5 7 7 7.5 7.75 8 8 8 8 9 9 9.5 10 10

15~16 5.5 6 6 6 6.5 6.5 6.5 7 7 7.5 7.75 8 8 8 8 9 9 9.5 10 10

17~18 5.5 6 6 6 6.5 6.5 6.5 7 7.5 7.5 7.75 8 8 8 8 9 9 9.5 10 10

19~20 5.5 6 6 6 6.75 7 7 7 7.5 7.5 7.75 8.25 8.25 8.75 9 9.75 9.75 9.75 10.25 10.25

21~22 5.75 6 6.25 6.25 6.75 7 7 7 7.5 7.5 7.75 8.25 8.25 8.75 9 9.75 9.75 9.75 10.25 10.25

23~24 5.75 6 6.25 6.25 6.75 7 7 7 7.5 7.5 7.75 8.25 8.25 8.75 9 9.75 9.75 9.75 10.25 10.25

25~26 5.75 6.25 6.25 6.25 6.75 7 7.5 7.5 7.75 8 8.25 8.75 9 9.75 9.75 9.75 9.75 9.75 10.25 10.25

27~28 5.75 6.25 6.25 6.25 6.75 7 7.5 7.5 7.75 8 8.25 8.75 9 9.75 9.75 9.75 9.75 9.75 10.25 10.25

29~30 5.75 6.25 6.25 6.75 6.75 7 7.5 7.5 7.75 8 8.25 8.75 9 9.75 9.75 9.75 9.75 9.75 10.25 10.25

31~32 5.75 6.25 6.25 6.75 6.75 7 7.5 7.5 7.75 8 8.25 8.75 9 9.75 9.75 9.75 9.75 9.75 10.25 10.25

33~34 5.75 6.25 6.25 6.75 6.75 7.5 7.5 7.5 7.75 8.25 8.25 8.75 9 9.75 9.75 9.75 9.75 9.75 10.25 10.25

35~36 6.25 6.75 6.75 7.25 7.25 7.5 7.5 7.75 8.25 8.25 8.75 9 9 9.75 9.75 9.75 9.75 9.75 10.25 10.25

37~38 6.25 6.75 6.75 7.25 7.75 7.75 7.75 8.25 8.25 8.25 8.75 9 9 9.75 9.75 9.75 9.75 9.75 10.25 10.25

39~40 6.25 6.75 6.75 7.25 7.75 7.75 7.75 8.25 8.25 8.25 8.75 9 9 9.75 9.75 9.75 10.25 10.25 10.75 10.75


DN0981084 Issue 02D


DND 56 (128)))


HSUPA data UEs

per HSUPA

scheduler


30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9 46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58

41~44 6.25 6.75 6.75 7.25 7.75 7.75 7.75 8.25 8.25 8.25 8.75 9 9 9.75 9.75 9.75 10.25 10.25 10.75 10.75

45~48 6.25 6.75 6.75 7.25 7.75 7.75 7.75 8.25 8.25 8.25 8.75 9 9 9.75 9.75 9.75 10.25 10.25 10.75 10.75

49~52 6.25 6.75 6.75 7.25 7.75 7.75 7.75 8.25 8.25 8.25 8.75 9 9 9.75 9.75 9.75 10.25 10.25 10.75 10.75

53~56 6.25 6.75 6.75 7.25 7.75 7.75 7.75 8.25 8.25 8.25 8.75 9 9 9.75 9.75 9.75 10.25 10.25 10.75 10.75

57~60 6.25 6.75 6.75 7.75 7.75 7.75 7.75 8.25 8.25 8.25 8.75 9 9 9.75 9.75 9.75 10.25 10.25 10.75 10.75

61~64 6.75 6.75 7.25 7.75 7.75 7.75 7.75 8.25 8.25 8.25 8.75 9.75 9.75 10.25 10.25 10.25 10.75 10.75 10.75 10.75

65~68 6.75 6.75 7.25 7.75 7.75 7.75 7.75 8.25 8.25 9.25 9.25 9.75 9.75 10.25 10.25 10.75 10.75 10.75 10.75 10.75

69~72 6.75 6.75 7.25 7.75 7.75 8.25 8.25 8.25 8.75 9.25 9.25 9.75 9.75 10.25 10.25 10.75 10.75 10.75 10.75 10.75

73~76 6.75 6.75 7.25 7.75 7.75 8.25 8.25 8.75 8.75 9.25 9.25 9.75 9.75 10.25 10.75 10.75 10.75 10.75 10.75 10.75

77~80 6.75 7.25 7.25 7.75 7.75 8.75 8.75 8.75 9.25 9.25 9.75 9.75 9.75 10.25 10.75 10.75 10.75 11.25 11.75 11.75

81~100 6.75 7.25 7.25 7.75 7.75 8.75 8.75 8.75 9.25 9.25 9.75 9.75 9.75 10.25 10.75 10.75 10.75 11.25 11.75 11.75

101~120 7.75 7.75 8.75 8.75 8.75 8.75 9.75 9.75 9.75 9.75 10.25 10.25 10.25 10.75 10.75 10.75 10.75 11.25 11.75 11.75

121~160 8.75 8.75 8.75 9.75 9.75 9.75 9.75 10.75 10.75 10.75 10.75 11.75 11.75 11.75 11.75 11.75 11.75 11.75 12.75 12.75

161~200 9 9.75 9.75 9.75 9.75 10.75 10.75 10.75 10.75 11.75 11.75 11.75 12.75 12.75 12.75 12.75 12.75 12.75 13.75 13.75

201~240 10 10 10 10.75 10.75 10.75 11.75 11.75 11.75 11.75 12.75 12.75 12.75 13.75 13.75 13.75 13.75 13.75 13.75 14.25



57 (128)))



Table 23 HSUPA resource allocation in number of subunits for System Module Rel.2 (no-F-DPCH 2ms TTI users)

HSUPA data 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 20.3 21.7 23.2 24.6 26.1 27.5 29

1 0.25 0.5 0.75 0.75 0.75 N/A N/A N/A N/A 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 0.25 0.5 0.75 0.75 1 1.75 1.75 1.75 1.75 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 0.25 0.5 1 1.5 1.5 1.75 1.75 1.75 1.75 2 2.75 2.75 2.75 3.75 3.75 3.75 3.75 N/A N/A N/A N/A

5~6 0.5 0.75 1 1.5 1.5 1.75 1.75 2 2 2 2.75 2.75 2.75 3.75 3.75 3.75 3.75 4 4.75 4.75 4.75

7~8 0.5 0.75 1.5 1.5 1.5 1.75 2 2 2 2 2.75 2.75 2.75 3.75 3.75 3.75 3.75 4 4.75 4.75 4.75

9~10 0.5 1 1.5 1.75 2 2.25 2.25 2.25 2.75 2.75 3 3 3.75 3.75 3.75 3.75 4.5 5 5 5 5.5

11~12 0.75 1 1.75 1.75 2 2.25 2.5 2.5 2.75 2.75 3 3 3.75 3.75 3.75 4.5 4.5 5 5 5 5.5

13~14 0.75 1 1.75 1.75 2 2.25 2.5 2.5 2.75 2.75 3 3 3.75 3.75 3.75 4.5 4.75 5.25 5.25 5.25 5.5

15~16 1 1 2 2.25 2.5 2.5 2.75 2.75 2.75 3 3 3 3.75 3.75 3.75 4.5 4.75 5.25 5.25 5.25 5.5

17~18 1 1.25 2 2.25 2.5 2.5 2.75 2.75 3 3.25 3.5 4 4 4 4.75 4.75 4.75 5.25 5.25 5.75 6.25

19~20 1 1.25 2 2.25 2.5 2.5 2.75 2.75 3 3.25 3.75 4.25 4.25 4.25 4.75 4.75 4.75 5.25 5.75 5.75 6.25

21~22 1.25 1.25 2 2.25 2.5 2.5 2.75 2.75 3 3.25 3.75 4.25 4.25 4.25 4.75 4.75 4.75 5.25 5.75 5.75 6.25

23~24 1.25 1.5 2 2.5 2.5 2.5 2.75 3 3 3.25 3.75 4.25 4.25 4.5 4.75 4.75 4.75 5.25 5.75 5.75 6.25

25~26 1.5 1.5 2 2.5 2.5 2.5 2.75 3 3 3.25 3.75 4.25 4.5 4.5 4.75 4.75 4.75 5.25 5.75 6.25 6.75

27~28 1.5 1.5 2 2.5 2.5 2.5 2.75 3.75 3.75 3.75 3.75 4.25 4.5 4.5 4.75 4.75 4.75 5.25 5.75 6.25 6.75

29~30 1.5 1.5 2.5 2.5 2.5 3 3.25 3.75 3.75 3.75 3.75 4.25 4.5 4.5 4.75 4.75 4.75 5.25 5.75 6.25 6.75

31~32 1.75 1.75 2.5 3 3 3 3.75 3.75 3.75 3.75 4.25 4.25 4.5 4.5 5 5 5 5.25 5.75 6.25 6.75

33~34 1.75 2 2.5 3 3.5 3.5 3.75 3.75 3.75 4.25 4.25 4.25 4.75 5 5 5 5 5.25 5.75 6.25 6.75

35~36 2 2 2.75 3 3.5 3.5 3.75 4 4 4.25 4.25 4.75 4.75 5 5.25 5.25 5.75 5.75 6.25 6.25 6.75

37~38 2 2.25 2.75 3 3.5 3.5 3.75 4 4 4.25 4.25 4.75 4.75 5 5.25 5.25 5.75 5.75 6.25 6.25 6.75

39~40 2 2.25 2.75 3 3.5 3.5 4 4 4 4.25 4.25 4.75 5.25 5.25 5.25 5.25 5.75 5.75 6.25 6.75 7.25


DN0981084 Issue 02D


DND 58 (128)))

Table 23 HSUPA resource allocation in number of subunits for System Module Rel.2 (no-F-DPCH 2ms TTI users) -cont.

HSUPA data 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 20.3 21.7 23.2 24.6 26.1 27.5 29

41~44 2.25 2.5 3 3 4 4 4 4 4 4.25 4.25 4.75 5.25 5.25 5.25 5.25 5.75 6.25 6.25 6.75 7.25

45~48 2.5 2.5 3 3.5 4 4 4 4 4.5 4.5 4.75 5.25 5.25 5.75 5.75 5.75 5.75 6.25 6.25 6.75 7.25

49~52 2.75 3 3.5 3.5 4 4.5 4.5 4.5 4.5 4.5 4.75 5.25 5.25 5.75 5.75 6 6.25 6.25 6.75 6.75 7.25

53~56 3 3.25 4 4 4 4.5 4.5 4.5 4.5 4.5 5.25 5.75 5.75 5.75 5.75 6 6.25 6.75 6.75 7.25 7.25

57~60 3 3.5 4 4 4.5 4.5 4.5 4.75 4.75 4.75 5.25 5.75 5.75 5.75 5.75 6 6.25 6.75 6.75 7.25 7.25

61~64 3.25 3.5 4 4.5 4.5 5 5 5.5 5.5 5.5 6 6 6 6 6.25 6.5 6.75 6.75 7.25 7.25 7.75

65~68 3.5 3.75 4 4.75 5 5.5 5.5 5.5 6 6 6 6.25 6.5 6.75 6.75 6.75 6.75 6.75 7.75 8.25 8.25

69~72 3.75 4 4 4.75 5 5.5 5.5 5.5 6 6 6 6.5 6.5 7 7 7.5 7.5 7.75 7.75 8.25 8.75

73~76 4 4.25 4.5 5 5 5.5 5.5 5.5 6 6 6 6.5 6.5 7 7.5 7.5 7.5 7.75 7.75 8.25 8.75

77~80 4 4.25 4.5 5 5 5.5 5.5 5.5 6 6 6 6.5 6.5 7 7.5 7.5 7.5 7.75 7.75 8.25 8.75

81~100 5 5 5 5 6 6.5 7 7 7.5 8 8 8 8 8 8 8.5 8.75 8.75 9.25 9.25 9.75

101~120 6 6 6 6 7 7.5 8 8 8 8.5 8.5 8.5 9 9 9 9 9.25 9.75 9.75 9.75 10.25

121~160 8 8 8 8 8 8 9 10 10.5 10.5 10.5 10.5 11 11 11 11 11.25 11.75 11.75 11.75 12

161~200 10 10 10 10 10 10 10 11 11.75 11.75 11.75 12 12.75 12.75 12.75 13.25 13.75 14.25 14.25 14.25 14.75

201~240 12 12 12 12 12 12 12 12 13 14 14 14 14.5 14.5 15 15 15 15 N/A N/A N/A



59 (128)))




HSUPA data UEs

per HSUPA scheduler


30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9 46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58




5~6 5.25 5.75 5.75 5.75 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

7~8 5.25 5.75 5.75 5.75 6 7 7 7 7.75 7.75 7.75 8 N/A N/A N/A N/A N/A N/A N/A N/A

9~10 6 6 6.5 6.5 6.5 7 7 7 7.75 8 8 8 8.5 9 9 9 9.75 9.75 9.75 9.75

11~12 6 6 6.5 6.5 6.5 7 7 8 8 8 8.25 8.25 8.75 9 9 9 9.75 9.75 10 10

13~14 6 6 6.5 6.5 6.5 7 7 8 8 8 8.25 8.25 8.75 9 9 9 9.75 9.75 10 10

15~16 6 6 6.5 6.75 6.75 7 7 8 8 8 8.25 8.25 8.75 9.25 9.25 9.25 9.75 9.75 10 10

17~18 6.25 6.25 6.5 6.75 6.75 7 7 8 8 8 8.25 8.25 8.75 9.25 9.25 9.25 9.75 9.75 10 10

19~20 6.75 6.75 6.75 6.75 7.75 7.75 7.75 8.25 8.75 8.75 8.75 8.75 9 9.25 9.25 9.25 9.75 9.75 10 10

21~22 6.75 6.75 6.75 6.75 7.75 7.75 7.75 8.25 8.75 8.75 8.75 8.75 9 9.25 9.25 9.25 10 10 11 11

23~24 6.75 6.75 6.75 6.75 7.75 7.75 8.25 8.25 8.75 8.75 8.75 8.75 9.25 9.25 9.25 10 10 10 11 11

25~26 6.75 6.75 6.75 6.75 7.75 7.75 8.25 8.25 8.75 8.75 8.75 8.75 9.25 9.25 10 10 10 10 11 11.25

27~28 6.75 6.75 6.75 7.5 7.75 8.25 8.25 8.25 8.75 8.75 8.75 8.75 9.25 9.25 10 10 10 10 11 11.25

29~30 6.75 6.75 6.75 7.5 7.75 8.25 8.75 8.75 8.75 8.75 8.75 8.75 9.25 10 10 10 10 10 11 11.25

31~32 6.75 6.75 6.75 7.5 7.75 8.25 8.75 8.75 9 9 9.25 9.25 9.25 10 10 10 10 10 11 11.25

33~34 6.75 6.75 6.75 7.5 7.75 8.25 8.75 8.75 9 9 9.25 9.25 9.25 10 10 10 10 10 11 11.25

35~36 7.25 7.25 7.25 7.5 7.75 8.25 8.75 8.75 9 9.25 9.25 9.25 9.75 10 10 10 10 10 11 11.25

37~38 7.25 7.25 7.25 7.75 8.25 8.25 8.75 8.75 9 9.25 9.25 9.25 9.75 10 10 10 10 10 11 11.25

39~40 7.25 7.25 7.75 7.75 8.25 8.25 8.75 8.75 9 9.25 9.25 9.75 9.75 10.5 11 11 11 11 11 11.25


DN0981084 Issue 02D


DND 60 (128)))


HSUPA data UEs

per HSUPA

scheduler


30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9 46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58

41~44 7.25 7.25 7.75 8 8.25 8.25 8.75 8.75 9 9.25 9.25 9.75 10 10.5 11 11 11 11.25 11.75 12.25

45~48 7.25 7.25 7.75 8 8.25 8.75 8.75 9.25 9.25 9.75 9.75 9.75 10.5 10.75 11 11 11 11.25 11.75 12.25

49~52 7.75 7.75 7.75 8 8.25 8.75 8.75 9.25 9.25 9.75 9.75 9.75 10.5 11 11 11.25 11.25 11.25 11.75 12.25

53~56 7.75 7.75 8.25 8.75 8.75 9.25 9.75 9.75 10.25 10.25 10.75 10.75 10.75 11 11 11.75 11.75 11.75 11.75 12.25

57~60 7.75 7.75 8.25 8.75 8.75 9.25 9.75 10.25 10.25 10.25 10.75 10.75 10.75 11.25 11.25 11.75 11.75 11.75 12.25 12.25

61~64 8.25 8.25 8.75 8.75 9.25 9.75 10.25 10.25 10.25 10.25 10.75 11.25 11.25 11.25 11.75 11.75 11.75 11.75 12.25 12.25

65~68 8.75 9.25 9.25 9.75 9.75 9.75 10.25 10.25 10.25 10.25 10.75 11.25 11.25 11.25 11.75 11.75 11.75 11.75 12.25 12.25

69~72 8.75 9.25 9.25 9.75 9.75 9.75 10.25 10.25 10.25 10.75 10.75 11.25 11.25 11.25 11.75 11.75 11.75 11.75 12.25 12.25

73~76 9.25 9.25 9.75 9.75 9.75 9.75 10.25 10.25 10.25 10.75 10.75 11.25 11.25 11.75 12.75 12.75 12.75 12.75 13.25 13.75

77~80 9.25 9.75 9.75 9.75 9.75 9.75 10.25 10.25 10.25 10.75 11 11.25 11.75 11.75 12.75 12.75 12.75 12.75 13.25 13.75

81~100 9.75 9.75 10.25 10.25 10.75 11.25 11.25 11.25 11.75 11.75 11.75 11.75 12.75 12.75 12.75 13.75 13.75 14.25 14.75 14.75

101~120 10.75 10.75 11.25 11.25 11.75 11.75 12.25 12.75 12.75 13.25 13.25 13.25 13.75 13.75 13.75 13.75 13.75 14.25 14.75 14.75

121~160 12.75 12.75 12.75 13.25 13.25 13.75 13.75 14.25 14.25 14.75 14.75 15 N/A N/A N/A N/A N/A N/A N/A N/A

161~200 14.75 14.75 15 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A




61 (128)))



Table 24 HSUPA resource allocation in number of subunits for System Module Rel.2 (F-DPCH 10ms TTI users)

HSUPA data UEs

per HSUPA scheduler


<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15.9 17.4 18.8 20.3 21.7 23.2 24.6 26.1 27.5

1 0.25 0.5 N/A N/A N/A N/A N/A N/A N/A 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 0.25 0.5 0.5 0.5 N/A N/A N/A N/A N/A 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 0.25 0.5 0.5 0.5 0.75 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 N/A N/A N/A

5~6 0.25 0.5 0.75 0.75 0.75 1 1.5 1.5 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

7~8 0.25 0.5 0.75 0.75 1 1 1.5 1.5 2 2 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

9~10 0.25 0.75 1 1 1 1 1.5 1.5 2 2 2.5 2.5 N/A N/A N/A N/A N/A N/A N/A N/A N/A

11~12 0.5 0.75 1 1 1 1.5 1.75 2 2 2 2.5 2.5 3 3 N/A N/A N/A N/A N/A N/A N/A

13~14 0.5 0.75 1 1 1.5 1.5 1.75 2 2 2 2.5 2.5 3 3 3.5 4 N/A N/A N/A N/A N/A

15~16 0.5 0.75 1 1 1.5 1.5 2 2 2 2 2.5 2.5 3 3 3.5 4 4 4 N/A N/A N/A

17~18 0.5 0.75 1 1 1.5 1.5 2 2 2 2 2.5 2.5 3 3 3.5 4 4 4 4 4 N/A

19~20 0.5 0.75 1 1.5 1.5 1.5 2 2 2 2 2.5 2.5 3 3 3.5 4 4 4 4 4 4

21~22 0.75 0.75 1 1.5 1.5 1.5 2 2 2 2.5 2.5 3 3 3 3.5 4 4 4 4 5 5

23~24 0.75 1 1 1.5 1.5 1.5 2 2 2 2.5 3 3 3 3 3.5 4 4 4 4 5 5

25~26 0.75 1 1.5 1.5 1.75 1.75 2 2 2 2.5 3 3 3 3 3.5 4 4 4 4 5 5

27~28 0.75 1 1.5 1.5 1.75 1.75 2 2 2.5 2.5 3 3 3 3 3.5 4 4 4 4 5 5

29~30 0.75 1 1.5 1.75 1.75 2 2 2.5 2.5 2.5 3 3 3 3 3.5 4 4 4 4 5 5

31~32 1 1 1.5 1.75 2 2 2.5 2.5 3 3 3 3 3 3 3.5 4 4 4 4 5 5

33~34 1 1 1.5 1.75 2 2 2.5 2.5 3 3 3 3 3 3.5 3.5 4 4 4 4 5 5

35~36 1 1 1.5 1.75 2 2 2.5 2.5 3 3 3 3 3.5 3.5 3.5 4 4 4 4 5 5

37~38 1 1 1.5 1.75 2 2 2.5 2.5 3 3 3 3.5 3.5 3.5 3.5 4 4 4 4 5 5

39~40 1 1 1.5 1.75 2 2.5 2.5 2.5 3 3 3 3.5 3.5 3.5 3.5 4 4 4 4 5 5


DN0981084 Issue 02D


DND 62 (128)))



scheduler


<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15.9 17.4 18.8 20.3 21.7 23.2 24.6 26.1 27.5

41~44 1.25 1.5 2 2 2.5 2.5 2.5 3 3 3 3 3.5 3.5 4 4 4 4 4 5 5 6

45~48 1.25 1.5 2 2 2.5 2.5 3 3 3 3 3 3.5 3.5 4 4 4 4 4 5 5 6

49~52 1.5 1.75 2 2 2.5 2.5 3 3 3 3 3.5 3.5 4 4 4 4 4.5 4.5 5 5 6

53~56 1.5 1.75 2 2 2.5 2.5 3 3 3 3.5 3.5 3.5 4 4 4 4.5 4.5 4.5 5 5 6

57~60 1.5 1.75 2 2 2.5 2.5 3 3 3.5 3.5 3.5 4 4 4 4 4.5 4.5 4.5 5 6 6

61~64 1.75 2 2 2 3 3 3 3.5 3.5 3.5 3.5 4 4 4 4.5 4.5 5 5 6 6 6

65~68 1.75 2 2 2 3 3 3 3.5 3.5 3.5 3.5 4 4 4.5 4.5 4.5 5 5 6 6 6

69~72 2 2 2 2 3 3 3 3.5 3.5 4 4 4 4 4.5 4.5 4.5 5 5 6 6 6

73~76 2 2 2 2 3 3 3.5 3.5 3.5 4 4 4 4.5 4.5 4.5 5 5 5 6 6 6

77~80 2 2 2 2 3 3 3.5 3.5 3.5 4 4 4 4.5 4.5 4.5 5 5 5 6 6 6

81~100 2.5 2.75 3 3 3 3.5 4 4 4 4 4 4.5 4.5 4.5 4.5 5 5 5 6 6 6

101~120 3 3 3 3 3 4 4 4 4.5 4.5 5 5 5 5.5 5.5 5.5 5.5 5.5 6 6 6

121~160 4 4 4 4 4 4 5 5 5 6 6 6 6 6 6.5 6.5 6.5 7 7 7 7.5

161~200 5 5 5 5 5 5 5 6 6 6 7 7 7 7 7 7.5 7.5 8 8 8 8

201~240 6 6 6 6 6 6 6 6 7 7 7 7.5 7.5 8 8 8 8 8.5 8.5 9 9



63 (128)))




HSUPA data UEs

per HSUPA scheduler


29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9 46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58

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 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 N/A N/A N/A N/A N/A N/A N/A N/A N/A








19~20 5 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

21~22 5 5 5 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

23~24 5 5 5 6 6 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

25~26 5 5 5 6 6 6 6 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

27~28 5 5 5 6 6 6 7 7 7 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

29~30 5 5 6 6 6 6 7 7 7 7 7.5 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

31~32 5 5 6 6 6 6 7 7 7 7 7.5 7.5 8 N/A N/A N/A N/A N/A N/A N/A N/A

33~34 5 5 6 6 6 6 7 7 7 7 7.5 7.5 8 8 8 N/A N/A N/A N/A N/A N/A

35~36 5 5 6 6 6 6 7 7 7 7 7.5 7.5 8 8 8 8 8 N/A N/A N/A N/A

37~38 5 5 6 6 6 6 7 7 7 7 7.5 7.5 8 8 8 8 8 8 8 N/A N/A

39~40 5 5 6 6 6 6 7 7 7 7 7.5 7.5 8 8 8 8 8 8 8 9 9


DN0981084 Issue 02D


DND 64 (128)))


HSUPA data UEs

per HSUPA scheduler


29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9 46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58

41~44 6 6 6 6 6 6 7 7 7 7 7.5 8 8 8 8 8 9 9 9 9 9

45~48 6 6 6 6 6 6 7 7 7 7 7.5 8 8 8 8 8 9 9 9 9 9

49~52 6 6 6 6 6 6 7 7 7 7 7.5 8 8 8 8 8 9 9 9 9 9

53~56 6 6 6 6 6 6 7 7 7 7 8 8 8 8 8 8 9 9 9 9 9

57~60 6 6 6 6 6 6 7 7 7 7 8 8 8 8 8 8 9 9 9 9 9

61~64 6 6 6 6 6 7 7 7 7 7.5 8 8 8 8 9 9 9 9 9 9 9

65~68 6 6 6 6 6 7 7 7 7 7.5 8 8 8 8 9 9 9 9 9 9 9

69~72 6 6 6 6 6 7 7 7 7 7.5 8 8 8 8 9 9 9 9 9 9 9

73~76 6 6 6 6 7 7 7 7 7 7.5 8 8 8 8 9 9 9 9 9 9 9

77~80 6 6 6 7 7 7 7 7 7 8 8 8 8 8 9 9 9 9 10 10 10

81~100 6 6 7 7 7.5 7.5 8 8 8 8 8 9 9 9 10 10 10 10 10 10 10

101~120 6 7 7 7 7.5 7.5 8 8 8 8 9 9 9 9 10 10 10 10 10 10 10

121~160 7.5 7.5 8 8 8 8 8 9 9 9 9 10 10 10 10 11 11 11 11 11 11

161~200 8.5 8.5 8.5 9 9 9 9.5 10 10 10 11 11 11 11 11 11 12 12 12 12 12

201~240 9 9.5 9.5 10 10 10 10 11 11 11 11 11 11 12 12 12 12 13 13 13 13



65 (128)))



Table 25 HSUPA resource allocation in number of subunits for System Module Rel.2 (no-F-DPCH 10ms TTI users)

HSUPA data UEs

per HSUPA scheduler


<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15.9 17.4 18.8 20.3 21.7 23.2 24.6 26.1 27.5

1 0.25 0.5 0.5 N/A N/A N/A N/A N/A N/A 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 0.25 0.5 0.5 0.75 N/A N/A N/A N/A N/A 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 0.25 0.5 0.75 0.75 1 1 1.5 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

5~6 0.5 0.75 0.75 0.75 1 1.5 1.5 1.75 2 2 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

7~8 0.5 0.75 1 1 1.5 1.75 1.75 2 2 2 2.5 2.75 2.75 N/A N/A N/A N/A N/A N/A N/A N/A

9~10 0.5 1 1 1 1.75 1.75 1.75 2 2 2.75 2.75 2.75 3.5 3.5 4.25 N/A N/A N/A N/A N/A N/A

11~12 0.75 1 1.5 1.5 1.75 1.75 2 2 2.75 2.75 2.75 2.75 3.5 3.5 4.25 4.25 4.25 4.25 N/A N/A N/A

13~14 0.75 1 1.5 1.5 1.75 2 2 2.75 2.75 3 3 3 3.5 3.75 4.25 4.25 4.25 4.75 4.75 5.75 5.75

15~16 1 1.5 1.5 1.5 1.75 2 2 2.75 2.75 3 3 3 3.5 3.75 4.5 4.5 5 5 5 5.75 5.75

17~18 1 1.5 1.5 1.5 1.75 2 2.75 2.75 2.75 3 3 3.5 3.5 3.75 4.5 4.5 5 5 5 5.75 5.75

19~20 1 1.5 1.75 1.75 1.75 2.75 2.75 2.75 3 3 3 3.5 3.75 3.75 4.75 4.75 5 5 5.75 6.25 6.25

21~22 1.25 1.5 1.75 1.75 2 2.75 2.75 2.75 3 3 3.5 3.75 3.75 4.75 4.75 4.75 5 5 5.75 6.25 6.25

23~24 1.25 1.75 1.75 2 2 2.75 2.75 2.75 3 3 3.5 3.75 3.75 4.75 4.75 4.75 5 5.5 6 6.5 6.5

25~26 1.5 2 2 2 2 2.75 2.75 2.75 3 3 3.5 4 4 4.75 4.75 4.75 5 5.5 6 6.5 6.5

27~28 1.5 2 2.5 2.5 2.5 2.75 2.75 2.75 3 3 3.5 4 4 4.75 4.75 5 5 5.5 6 6.5 6.5

29~30 1.5 2 2.5 2.5 2.5 2.75 3 3 3 3 4 4 4 4.75 5 5 5.5 5.5 6 6.5 6.5

31~32 1.75 2 2.5 2.5 2.5 3 3 3 3.5 3.5 4 4 4 5 5 5 5.5 5.5 6 6.5 6.5

33~34 1.75 2 2.5 2.5 2.5 3 3.5 3.5 3.5 3.5 4 4 4 5 5 5 5.5 5.5 6.5 6.5 6.5

35~36 2 2 2.5 2.5 2.5 3 3.5 3.5 3.5 4 4 4 5 5 5 5.5 5.5 6 6.5 7 7

37~38 2 2.5 2.75 2.75 3 3 3.5 3.5 3.5 4 4 4.5 5 5 5 5.5 5.5 6 6.5 7 7

39~40 2 2.5 2.75 2.75 3 3 3.5 3.5 3.5 4 4 4.5 5 5 5 5.5 5.5 6 6.5 7 7


DN0981084 Issue 02D


DND 66 (128)))

Table 25 HSUPA resource allocation in number of subunits for System Module Rel.2 (no-F-DPCH 10ms TTI users)-cont.

HSUPA data UEs per HSUPA scheduler


<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15.9 17.4 18.8 20.3 21.7 23.2 24.6 26.1 27.5

41~44 2.25 2.5 3 3 3 3.75 3.75 4 4 4 4.5 4.75 5 5.5 6 6 6 6.5 6.5 7 7

45~48 2.5 2.75 3.5 3.5 3.75 3.75 4 4 4.75 4.75 4.75 4.75 5.75 5.75 6 6 6 6.5 7 7 7

49~52 2.75 3 3.5 3.5 3.75 4 4.5 4.5 5 5 5 5 5.75 6 6 6.5 6.5 6.5 7 7.5 7.5

53~56 3 3.25 3.75 3.75 4 4 4.5 4.5 5 5 5 5 6 6 6 6.5 6.5 7 7 7.5 7.5

57~60 3 3.5 3.75 4 4 4 4.5 4.5 5 5 5 5 6 6 6 6.5 6.5 7 7 7.5 7.5

61~64 3.25 3.75 4 4 4.75 4.75 5 5 5 5.5 6 6 6 6.5 6.5 7 7 7.5 7.5 8 8

65~68 3.5 3.75 4.5 4.5 4.75 4.75 5 5 5 5.5 6 6 6 6.5 6.5 7 7 7.5 8 8 8.5

69~72 3.75 4 4.5 4.5 4.75 5 5 5.5 5.5 6 6 6 6 6.5 6.5 7.5 7.5 7.5 8 8 8.5

73~76 4 4.5 4.5 4.5 5 5 5.5 5.5 6 6 6 6.5 6.5 7 7 7.5 8 8 8.5 8.5 9

77~80 4 4.5 4.5 5 5 5.5 5.5 6 6 6 6 6.5 7 7.5 8 8.5 8.5 8.5 9 9 9

81~100 5 5 6 6 6 6.5 6.5 7 8 8 8 8 8 8 8.5 8.5 8.5 9 9 9.5 9.5

101~120 6 6 6 6 7 7 7 7 8 8 8.5 8.5 8.5 9 9 10 10 10 10 11 11

121~160 8 8 8 8 8 9 9 9 10 10 10 10 10 11 11 11 11 12 12 12 12

161~200 10 10 10 10 10 10 10 11 11 11 12 12 12 12 12.75 12.75 13.75 13.75 13.75 15 15

201~240 12 12 12 12 12 12 12 12 13 13 14 14 14 14 14 15 15 15 N/A N/A N/A



67 (128)))





scheduler


29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9 46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58









15~16 6.5 7 7.5 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

17~18 6.5 7 7.5 7.5 7.5 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

19~20 6.75 7 7.5 7.5 8 8.75 8.75 8.75 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

21~22 6.75 7 7.5 7.5 8 8.75 8.75 8.75 9 9 9 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

23~24 7 7.5 7.5 7.5 8 8.75 8.75 8.75 9 9 9 9 10 10 N/A N/A N/A N/A N/A N/A N/A

25~26 7 7.5 7.5 7.5 8 8.75 8.75 8.75 9 9 9 9 10 10.5 11 11 N/A N/A N/A N/A N/A

27~28 7 7.5 7.5 7.5 8 8.75 9.5 9.5 9.5 9.5 10 10 10 10.5 11 11 11.5 11.5 11.5 N/A N/A

29~30 7 7.5 7.5 7.5 8 8.75 9.5 9.5 9.5 9.5 10 10 10 10.5 11 11 11.5 11.5 11.5 11.5 11.5

31~32 7 7.5 7.5 7.5 8 8.75 9.5 9.5 9.5 9.5 10 10 10 10.5 11 11 11.5 11.5 11.5 12 12

33~34 7 7.5 7.5 7.5 8 8.75 9.5 9.5 9.5 9.5 10 10 10 10.5 11 11 11.5 11.5 12 12.5 12.5

35~36 7.5 7.5 7.5 7.5 8.5 8.75 9.5 9.5 9.5 9.5 10 10 10 10.5 11 11 11.5 12 12 12.5 12.5

37~38 7.5 7.5 8.5 8.5 8.5 9.5 9.5 9.5 9.5 10 10 11 11 11 11 11 11.5 12 12 12.5 12.5

39~40 7.5 7.5 8.5 9 9 9.5 9.5 9.5 9.5 10 10 11 11 11.5 11.5 11.5 12 12 12.5 12.5 12.5


DN0981084 Issue 02D


DND 68 (128)))



scheduler


29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9 46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58

41~44 7.5 7.5 8.5 9 9 9.5 9.5 9.5 9.5 10 10 11 11 11.5 11.5 11.5 12 12 12.5 13.5 13.5

45~48 7.5 8.5 8.5 9 9 9.5 9.5 9.5 10 10 10 11 11 11.5 11.5 11.5 12 12 13 13.5 13.5

49~52 7.5 8.5 8.5 9 9 9.5 9.5 9.5 10 10 10.5 11 11 11.5 11.5 12 12.5 12.5 13 13.5 13.5

53~56 7.5 8.5 9 9 9 9.5 9.5 9.5 10 10 10.5 11 11 11.5 11.5 12 12.5 13 13 14 14

57~60 8 8.5 9 9 9 9.5 9.5 10 10 10 11 11 11 11.5 11.5 12 13 13 13.5 14 14

61~64 8 8.5 9 9.5 10 10 10 10.5 10.5 10.5 11 11 11 11.5 12 12 13.5 13.5 13.5 14 14

65~68 8.5 8.5 9.5 9.5 10 10 10.5 11 11 11 11.5 12 12 12.5 12.5 12.5 13.5 13.5 13.5 14 14

69~72 8.5 8.5 9.5 9.5 10.5 10.5 10.5 11.5 11.5 11.5 11.5 12.5 12.5 12.5 12.5 12.5 13.5 13.5 13.5 14 14

73~76 9.5 9.5 9.5 10 10.5 11 11 11.5 11.5 11.5 11.5 12.5 12.5 13 13.5 13.5 14 14 14.5 15 15

77~80 9.5 9.5 9.5 10 10.5 11 11 11.5 11.5 11.5 11.5 12.5 12.5 13 13.5 13.5 14 14 14.5 15 15

81~100 10 10.5 10.5 11 11 11 11.5 12 12.5 12.5 13 13.5 13.5 14 14 14 14.5 14.5 14.5 15 N/A

101~120 11 11 11.5 11.5 12 12 12 12.5 12.5 13 13.5 13.5 14 14 14.5 14.5 14.5 15 15 N/A N/A

121~160 13 13 13 14 14 14 15 15 15 15 15 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

160~200 14.75 15 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A




69 (128)))



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



<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15.9 17.4 18.8 20.3 21.7 23.2

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 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 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 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 N/A N/A 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 N/A N/A N/A N/A 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 N/A N/A N/A N/A N/A N/A

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 0.875 0.875 N/A N/A N/A N/A

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 1 1 1.125 1.125 N/A N/A

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 1 1 1.125 1.125 1.25 1.25

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 1 1 1.125 1.125 1.25 1.25

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 1 1 1.125 1.125 1.25 1.25

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.875 1 1 1.125 1.125 1.25 1.25

23~24 0.375 0.375 0.5 0.625 0.75 0.875 1 1 1 1 1 1 1 1 1.125 1.125 1.25 1.25

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 1.125 1.125 1.125 1.125 1.25 1.25

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 1.125 1.125 1.125 1.125 1.25 1.25

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 1.25 1.25 1.25 1.25 1.5 1.5

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 1.375 1.375 1.375 1.375 1.5 1.5

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 1.375 1.375 1.375 1.375 1.5 1.5

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 1.5 1.5 1.5 1.5 2 2

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 1.75 1.75 1.75 1.75 2 2

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 1.875 1.875 1.875 2 2 2.25


DN0981084 Issue 02D


DND 70 (128)))

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



<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15.9 17.4 18.8 20.3 21.7 23.2

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.875 1.875 1.875 2 2 2.25

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 2 2 2 2 2.25

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 2 2 2 2 2.25

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 2 2 2 2 2.25

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.125 2.125 2.125 2.125 2.125 2.25

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.125 2.125 2.125 2.125 2.125 2.25

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.25 2.25 2.25 2.25 2.25 2.25

69~72 1 1 1 1.125 1.25 1.5 1.625 1.75 1.875 2 2.125 2.25 2.25 2.25 2.25 2.25 2.25 2.25

73~76 1 1 1 1.125 1.25 1.5 1.625 1.75 2 2 2.125 2.375 2.375 2.5 2.625 2.75 2.875 3

77~80 1 1 1 1.125 1.375 1.5 1.75 1.875 2 2.125 2.25 2.375 2.5 2.625 2.75 2.875 3 3.125

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.75 2.875 3 3.125 3.25 3.375

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 3.125 3.25 3.375 3.5 3.625

121~140 1.75 1.75 1.75 1.75 1.75 2.125 2.25 2.375 2.5 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625

141~160 2 2 2 2 2 2.25 2.5 2.625 2.875 3 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125

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 4.125 4.25 4.375 4.5 4.625

201~240 3 3 3 3 3 3 3 3.25 3.625 3.625 3.875 4.125 4.375 4.5 4.75 4.875 5 5.125



71 (128)))



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


scheduler


24.6 26.1 27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9

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 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 N/A N/A N/A







17~18 1.25 1.25 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

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

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

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

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

27~28 1.25 1.25 1.5 1.5 1.75 1.75 2 2 2 2 2.25 2.25 N/A N/A N/A

29~30 1.5 1.75 1.75 1.75 1.75 1.75 2 2 2 2 2.25 2.25 2.5 2.5 N/A

31~32 1.5 1.75 1.75 1.75 1.75 1.75 2 2 2 2 2.25 2.25 2.5 2.5 2.75

33~34 1.5 1.75 1.75 1.75 1.75 1.75 2 2 2 2 2.25 2.25 2.5 2.5 2.75

35~36 2 2 2 2 2 2 2 2 2 2 2.25 2.25 2.5 2.5 2.75

37~38 2 2 2 2 2 2 2 2 2 2 2.25 2.25 2.5 2.5 2.75

39~40 2.25 2.25 2.5 2.5 2.625 2.625 2.625 2.75 2.75 2.75 2.75 3 3 3 3


DN0981084 Issue 02D


DND 72 (128)))

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

HSUPA data UEs

per HSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9

41~44 2.25 2.25 2.5 2.5 2.625 2.625 2.625 2.75 2.75 2.75 2.75 3 3 3 3

45~48 2.25 2.25 2.5 2.5 2.625 2.625 2.625 2.75 2.75 2.75 2.75 3 3 3 3

49~52 2.25 2.25 2.5 2.5 2.625 2.625 2.625 2.75 2.75 2.75 2.75 3 3 3 3

53~56 2.25 2.25 2.5 2.5 2.625 2.625 2.625 2.75 2.75 2.75 2.75 3 3 3 3

57~60 2.25 2.25 2.5 2.5 2.625 2.625 2.625 2.75 2.75 2.75 2.75 3 3 3 3

61~64 2.25 2.25 2.5 2.5 2.625 2.625 2.625 2.75 2.75 2.75 2.75 3 3 3 3

65~68 2.25 2.25 2.5 2.5 2.625 2.625 2.625 2.75 2.75 2.75 2.75 3 3 3 3

69~72 2.25 2.25 2.5 2.5 2.625 2.625 2.625 2.75 2.75 2.75 2.75 3 3 3 3

73~76 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

77~80 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25

81~100 3.5 3.625 3.75 3.875 4 4 4 4 4 4 4 4 4 4 4

101~120 3.75 3.875 4 4.125 4.25 4.375 4.5 4.625 4.75 4.75 4.75 4.75 4.75 4.75 4.75

121~140 3.75 3.875 4 4.125 4.25 4.375 4.5 4.625 4.75 4.75 4.75 4.75 4.75 4.75 4.75

141~160 4.25 4.375 4.5 4.625 4.75 4.875 5 5.125 5.25 5.375 5.5 5.625 5.75 5.875 6

161~200 4.75 4.875 5 5.125 5.25 5.375 5.5 5.625 5.75 5.875 6 6.125 6.25 6.375 6.5

201~240 5.25 5.375 5.5 5.75 5.875 6 6.125 6.25 6.25 6.5 6.625 6.625 6.75 7 7



73 (128)))



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

HSUPA data UEs

per HSUPA scheduler


46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58 59.45 60.9 62.35 63.8 65.25 66.7 68.15 69.6

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 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 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 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 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 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/A N/A N/A N/A N/A N/A

39~40 3 3 3 3.25 3.25 3.5 3.5 3.75 3.75 N/A N/A N/A N/A N/A N/A N/A N/A


DN0981084 Issue 02D


DND 74 (128)))


HSUPA data UEs

per HSUPA

scheduler


46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58 59.45 60.9 62.35 63.8 65.25 66.7 68.15 69.6

41~44 3 3 3 3.25 3.25 3.5 3.5 3.75 3.75 3.75 3.75 4 4 N/A N/A N/A N/A

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

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

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

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

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

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

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

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

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 4 4.25 4.25 4.25 4.25

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

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 4.75 4.75 4.75 4.75 4.75

121~140 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75

141~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 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 7.875 7.875 7.875 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 8.625 8.75 8.875 9 9.125



75 (128)))



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

HSUPA data UEs

per HSUPA scheduler


<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15.9 17.4 18.8 20.3 21.7 23.2

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 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 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 N/A 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 N/A N/A N/A N/A 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 1 N/A N/A N/A N/A N/A

9~10 0.25 0.375 0.375 0.5 0.5 0.5 0.625 0.625 0.75 0.875 1 1 1.125 1.25 1.25 N/A N/A N/A

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 1.125 1.25 1.375 1.375 1.5 1.5

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 1.125 1.25 1.375 1.375 1.5 1.625

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 1.125 1.25 1.375 1.5 1.5 1.625

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 1.125 1.25 1.5 1.5 1.625 1.625

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 1.125 1.25 1.5 1.5 1.625 1.625

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

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 1.25 1.375 1.5 1.625 1.75 1.75

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 1.375 1.375 1.5 1.625 1.75 1.875

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 1.5 1.5 1.625 1.75 1.75 2

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

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 1.625 1.625 1.75 1.75 1.875 2

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 1.625 1.625 1.75 1.75 1.875 2

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

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

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


DN0981084 Issue 02D


DND 76 (128)))


HSUPA data UEs

per HSUPA

scheduler


<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 15.9 17.4 18.8 20.3 21.7 23.2

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.875 1.875 1.875 1.875 2 2

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.125 2.125 2.125 2.125 2.125 2.125

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.25 2.25 2.25 2.25 2.25 2.25

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.375 2.375 2.375 2.375 2.375 2.375

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.375 2.5 2.625 2.625 2.625 2.625

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.5 2.625 2.75 2.75 2.75 2.75

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.5 2.625 2.75 2.875 3 3

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.625 2.75 2.875 3 3.125 3.125

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

77~80 2 2 2 2 2 2 2 2.125 2.25 2.375 2.5 2.625 2.75 2.875 3 3.125 3.25 3.375

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 3 3.25 3.25 3.375 3.5 3.625

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

121~140 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.625 3.625 3.625 3.75 3.75 3.75 3.75 3.75 3.875 4

141~160 4 4 4 4 4 4 4 4 4 4 4 4 4 4.125 4.25 4.375 4.5 4.625

161~200 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5.125 5.125 5.25

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



77 (128)))



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

HSUPA data UEs

per HSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9








13~14 1.625 1.75 1.75 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 1.75 1.875 1.875 2 2 2 N/A N/A N/A N/A N/A N/A N/A N/A N/A

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

19~20 1.75 1.875 2 2 2.125 2.25 2.25 2.375 2.375 2.5 2.5 N/A N/A N/A N/A

21~22 1.875 1.875 2 2 2.125 2.25 2.25 2.375 2.5 2.5 2.625 2.75 2.75 2.75 N/A

23~24 1.875 1.875 2 2.125 2.125 2.25 2.375 2.375 2.5 2.625 2.625 2.75 2.75 2.875 3

25~26 1.875 2 2 2.125 2.25 2.25 2.375 2.375 2.5 2.625 2.75 2.75 2.875 3 3

27~28 2 2 2.125 2.125 2.25 2.25 2.375 2.5 2.625 2.625 2.75 2.75 2.875 3 3

29~30 2.125 2.125 2.125 2.125 2.25 2.375 2.5 2.5 2.625 2.625 2.75 2.75 2.875 3 3.125

31~32 2.125 2.125 2.125 2.125 2.25 2.375 2.5 2.5 2.625 2.75 2.75 2.875 3 3 3.125

33~34 2.125 2.25 2.25 2.25 2.25 2.375 2.5 2.5 2.625 2.75 2.875 2.875 3 3 3.125

35~36 2.125 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.875 2.875 3 3.125 3.125

37~38 2.125 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.875 2.875 3 3.125 3.125

39~40 2.125 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.875 2.875 3 3.125 3.125


DN0981084 Issue 02D


DND 78 (128)))


HSUPA data UEs

per HSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9

41~44 2.125 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.875 2.875 3 3.125 3.125

45~48 2.125 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.875 2.875 3 3.125 3.125

49~52 2.25 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.875 2.875 3 3.125 3.125

53~56 2.375 2.375 2.375 2.375 2.375 2.375 2.5 2.5 2.625 2.75 2.875 2.875 3 3.125 3.125

57~60 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.75 2.875 2.875 3 3.125 3.125

61~64 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.875 2.875 3 3 3.125 3.25

65~68 3 3 3 3 3 3 3 3 3 3 3 3 3.125 3.125 3.25

69~72 3.125 3.125 3.125 3.125 3.125 3.125 3.125 3.125 3.125 3.125 3.125 3.125 3.125 3.25 3.25

73~76 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.25 3.375

77~80 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5

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

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

121~140 4.125 4.25 4.375 4.5 4.625 4.75 4.875 5 5.125 5.125 5.125 5.125 5.125 5.125 5.125

141~160 4.75 4.875 5 5.125 5.25 5.375 5.5 5.625 5.75 5.875 6 6.125 6.25 6.375 6.5

161~200 5.375 5.5 5.625 5.75 5.875 6 6.125 6.25 6.375 6.5 6.625 6.75 6.875 7 7.125

201~240 6.125 6.125 6.25 6.375 6.5 6.625 6.875 7 7.125 7.25 7.375 7.375 7.625 7.75 7.75



79 (128)))




HSUPA data UEs

per HSUPA

scheduler


46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58 59.45 60.9 62.35 63.8 65.25 66.7 68.15 69.6













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

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/A N/A N/A N/A N/A N/A

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/A N/A N/A N/A N/A N/A

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/A N/A N/A N/A N/A N/A

31~32 3.125 3.25 3.375 3.375 3.5 3.625 3.75 3.75 3.875 3.875 4 4 4 N/A N/A N/A N/A

33~34 3.25 3.25 3.375 3.5 3.625 3.625 3.75 3.75 3.875 4 4 4.125 4.25 4.25 4.25 N/A N/A

35~36 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 3.875 4 4.125 4.125 4.25 4.25 4.375 4.5 4.5

37~38 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 3.875 4 4.125 4.125 4.25 4.25 4.375 4.5 4.5

39~40 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 4 4.125 4.125 4.125 4.25 4.25 4.375 4.5 4.5


DN0981084 Issue 02D


DND 80 (128)))

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

HSUPA data UEs

per HSUPA

scheduler


46.4 47.8 49.2 50.7 52.2 53.6 55 56.5 58 59.4 60.9 62.3 63.8 65.2 66.7 68.1 69.6

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 4.375 4.5 4.5 4.5 4.5

45~48 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 4 4.125 4.125 4.25 4.375 4.5 4.625 4.75 4.75

49~52 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 4 4.125 4.125 4.25 4.375 4.5 4.625 4.75 4.75

53~56 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 4 4.125 4.125 4.25 4.375 4.5 4.625 4.75 4.75

57~60 3.25 3.375 3.375 3.5 3.625 3.625 3.75 3.875 4 4.125 4.125 4.25 4.375 4.5 4.625 4.75 4.75

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 4.375 4.5 4.625 4.75 4.75

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 4.375 4.5 4.625 4.75 4.75

69~72 3.375 3.5 3.5 3.625 3.75 3.75 3.875 4 4 4.125 4.125 4.25 4.375 4.5 4.625 4.75 4.75

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 4.375 4.5 4.625 4.75 4.75

77~80 3.5 3.5 3.625 3.625 3.75 3.875 3.875 4 4.125 4.25 4.25 4.375 4.375 4.5 4.625 4.75 4.75

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 4.625 4.75 4.75 4.875 4.875

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.125 5.125 5.125 5.125 5.125 5.125

121~140 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125

141~160 6.625 6.75 6.875 6.875 6.875 6.875 6.875 6.875 6.875 6.875 6.875 6.875 6.875 6.875 6.875 6.875 6.875

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 8.5 8.5 8.5 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 9.375 9.5 9.625 9.75 9.875



81 (128)))



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

HSUPA data 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 20.3 21.7 23.2 24.6 26.1

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 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 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.375 1.375 1.375 1.375 N/A N/A

5~6 0.125 0.25 0.5 0.5 0.625 0.75 0.875 1 1 1 1 1 1 1.375 1.375 1.375 1.375 1.625 1.625

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.375 1.375 1.375 1.375 1.625 1.625

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.625 1.625 1.625 1.625 1.625 1.625

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 1.875 2 2 2 2

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 1.875 2 2.125 2.25 2.25

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 1.875 2.125 2.125 2.25 2.5

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.75 1.875 2.125 2.25 2.25 2.5

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 1.875 2.125 2.25 2.375 2.5

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 1.875 2.125 2.25 2.375 2.5

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 1.875 2.125 2.25 2.375 2.5

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 1.875 2.125 2.25 2.375 2.5

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 1.875 2.125 2.25 2.375 2.5

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 1.875 2.125 2.25 2.375 2.5

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 1.875 2.125 2.25 2.375 2.5

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 1.875 2.125 2.25 2.375 2.5

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 1.875 2.125 2.25 2.375 2.5

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 1.875 2.125 2.25 2.375 2.5

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 1.875 2.125 2.25 2.375 2.5


DN0981084 Issue 02D


DND 82 (128)))


HSUPA data 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 20.3 21.7 23.2 24.6 26.1

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 1.875 2.125 2.25 2.375 2.5

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.875 1.875 2.125 2.25 2.375 2.5

49~52 0.75 0.75 0.875 1 1 1.25 1.5 1.625 1.875 2 2 2 2 2 2 2.125 2.25 2.375 2.5

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 2.25 2.25 2.25 2.375 2.5

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.375 2.375 2.375 2.375 2.375 2.5

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 2.5 2.5 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.625 2.625 2.625 2.625 2.625 2.625

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.875 2.875 2.875 2.875 2.875 2.875

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.875 3 3 3 3 3

77~80 1 1 1 1.25 1.375 1.5 1.625 1.75 2 2.125 2.375 2.5 2.75 2.875 3.125 3.125 3.125 3.125 3.125

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 3.25 3.375 3.5 3.75 3.875

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.125 3.25 3.375 3.625 3.875 4

121~140 1.75 1.75 1.75 1.75 1.75 1.875 2 2.125 2.25 2.375 2.5 2.75 2.875 3.125 3.25 3.375 3.625 3.875 4

141~160 2 2 2 2 2 2 2.5 2.5 2.625 2.75 2.875 3 3.125 3.25 3.375 3.625 3.875 4 4.125

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.625 3.75 3.875 4 4.125 4.375

201~240 3 3 3 3 3 3 3 3.125 3.125 3.625 3.625 3.75 3.875 4 4.125 4.25 4.375 4.5 4.625



83 (128)))




HSUPA data UEs

per HSUPA scheduler


27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9 46.4 47.8




5~6 1.625 1.75 2 2 2 2 N/A N/A N/A N/A 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.625 2.625 2.625 2.625 N/A

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

11~12 2 2 2 2 2 2 2 2.125 2.375 2.625 2.625 2.625 2.625 2.625 2.75

13~14 2.25 2.25 2.25 2.25 2.25 2.25 2.25 2.25 2.375 2.625 2.625 2.625 2.625 2.625 2.75

15~16 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.75

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

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

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

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

25~26 2.625 2.75 2.875 3 3 3.25 3.375 3.5 3.5 3.75 3.875 4 4 4.125 4.125

27~28 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4 4.25 4.25

29~30 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4 4.25 4.375

31~32 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4 4.25 4.375

33~34 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

35~36 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

37~38 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

39~40 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375


DN0981084 Issue 02D


DND 84 (128)))



scheduler


27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9 46.4 47.8

41~44 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

45~48 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

49~52 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

53~56 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

57~60 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

61~64 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

65~68 2.625 2.75 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

69~72 2.875 2.875 2.875 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

73~76 3 3 3 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

77~80 3.125 3.125 3.125 3.125 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375

81~100 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3.875 4 4.125 4.25 4.375

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

121~140 4.25 4.375 4.625 4.625 4.625 4.625 4.625 4.625 4.625 4.625 4.625 4.625 4.625 4.625 4.625

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

161~200 4.5 4.75 4.875 5.125 5.375 5.5 5.75 5.875 6.125 6.25 6.5 6.625 6.875 7 7.25

201~240 4.75 4.875 5 5.25 5.5 5.625 5.875 6 6.25 6.5 6.625 6.875 7 7.125 7.375



85 (128)))




HSUPA data UEs

per HSUPA

scheduler


49.2 50.7 52.2 53.6 55.0 56.5 58 59.4 60.9 62.35 63.8 65.25 66.7 68.1 69.6






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

11~12 2.875 3.125 3.125 3.125 3.375 3.375 3.375 3.5 3.625 3.625 3.625 3.875 3.875 4 4

13~14 2.875 3.125 3.125 3.125 3.375 3.375 3.375 3.5 3.625 3.625 3.625 3.875 3.875 4 4

15~16 2.875 3.125 3.125 3.125 3.375 3.375 3.375 3.5 3.625 3.625 3.625 3.875 3.875 4 4

17~18 2.875 3.125 3.125 3.125 3.375 3.375 3.375 3.5 3.625 3.625 3.625 3.875 4.125 4.25 4.25

19~20 3.25 3.25 3.25 3.25 3.375 3.375 3.375 3.5 3.625 3.625 3.625 3.875 4.125 4.25 4.25

21~22 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.625 3.625 3.625 3.875 4.125 4.25 4.25

23~24 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3.875 3.875 4.125 4.25 4.25

25~26 4.125 4.125 4.125 4.125 4.125 4.125 4.125 4.125 4.125 4.125 4.125 4.125 4.125 4.25 4.25

27~28 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5

29~30 4.5 4.5 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75 4.75

31~32 4.5 4.5 4.75 4.875 5 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125 5.125

33~34 4.5 4.5 4.75 4.875 5 5.125 5.25 5.25 5.375 5.375 5.375 5.375 5.375 5.375 5.375

35~36 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.75 5.75 5.75 5.75

37~38 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6 6

39~40 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375


DN0981084 Issue 02D


DND 86 (128)))


HSUPA data UEs

per HSUPA

scheduler


49.2 50.7 52.2 53.6 55.0 56.5 58 59.4 60.9 62.35 63.8 65.25 66.7 68.1 69.6

41~44 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

45~48 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

49~52 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

53~56 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

57~60 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

61~64 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

65~68 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

69~72 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

73~76 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

77~80 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

81~100 4.5 4.5 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

101~120 4.625 4.625 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

121~140 4.625 4.625 4.75 4.875 5 5.125 5.25 5.375 5.625 5.625 5.75 5.875 6 6.125 6.375

141~160 6.125 6.125 6.125 6.125 6.125 6.125 6.125 6.125 6.125 6.125 6.125 6.125 6.125 6.125 6.375

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

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



87 (128)))




HSUPA data 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 20.3 21.7 23.2 24.6 26.1

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 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 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.375 1.375 1.375 1.375 N/A N/A

5~6 0.125 0.25 0.5 0.5 0.625 0.75 0.875 1 1 1 1 1 1 1.375 1.375 1.375 1.375 1.625 1.625

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.375 1.375 1.375 1.375 1.625 1.625

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.625 1.625 1.625 1.625 1.625 1.625

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 1.875 2 2 2 2

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 1.875 2 2.125 2.25 2.25

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 1.875 2.125 2.125 2.25 2.5

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.75 1.875 2.125 2.25 2.25 2.5

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 1.875 2.125 2.25 2.375 2.5

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 2 2.125 2.25 2.375 2.5

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 2 2.125 2.25 2.375 2.5

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 2 2.125 2.25 2.375 2.5

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 2 2.125 2.25 2.375 2.5

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 2 2.125 2.25 2.375 2.5

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 2 2.125 2.25 2.375 2.5

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 2 2.125 2.25 2.375 2.5

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 2 2.125 2.25 2.375 2.5

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 2 2.125 2.25 2.375 2.5

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 2 2.125 2.25 2.375 2.5


DN0981084 Issue 02D


DND 88 (128)))

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

HSUPA data 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 20.3 21.7 23.2 24.6 26.1

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 2 2.125 2.25 2.375 2.5

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.125 2.125 2.125 2.25 2.375 2.5

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 2.25 2.25 2.25 2.375 2.5

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.375 2.375 2.375 2.5 2.5 2.5

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.625 2.625 2.625 2.625 2.625 2.625

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.75 2.75 2.75 2.75 2.75 2.75

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.875 2.875 2.875 2.875 2.875 2.875

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.125 3.125 3.125 3.125 3.125 3.125

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

77~80 2 2 2 2 2.125 2.25 2.375 2.5 2.625 2.75 2.875 3 3.125 3.25 3.375 3.375 3.375 3.375 3.375

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.625 3.75 3.875 4 4.125 4.25

101~120 3 3 3 3 3 3 3.125 3.25 3.375 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375 4.5 4.625

121~140 3.5 3.5 3.5 3.5 3.5 3.5 3.625 3.75 3.875 4 4.125 4.25 4.375 4.5 4.625 4.75 4.875 5 5.125

141~160 4 4 4 4 4 4 4 4 4.125 4.25 4.375 4.5 4.625 4.75 4.875 5 5.125 5.25 5.375

161~200 5 5 5 5 5 5 5 5 5 5 5.125 5.25 5.375 5.5 5.625 5.75 5.875 6 6.125

201~240 6 6 6 6 6 6 6 6 6 6 6 6 6.125 6.25 6.375 6.5 6.625 6.75 6.875



89 (128)))



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

HSUPA data UEs

per HSUPA

scheduler


27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9 46.4 47.8




5~6 1.625 1.75 2 2 2 2 N/A N/A N/A N/A 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.625 2.625 2.625 2.625 N/A

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

11~12 2 2 2 2 2 2 2 2.125 2.375 2.625 2.625 2.625 2.625 2.625 2.75

13~14 2.25 2.25 2.25 2.25 2.25 2.25 2.25 2.25 2.375 2.625 2.625 2.625 2.625 2.625 2.75

15~16 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.625 2.75

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

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

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

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

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

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

29~30 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

31~32 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

33~34 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

35~36 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

37~38 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

39~40 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5


DN0981084 Issue 02D


DND 90 (128)))


HSUPA data UEs

per HSUPA

scheduler


27.5 29 30.4 31.9 33.3 34.8 36.2 37.6 39.1 40.6 42 43.4 44.9 46.4 47.8

41~44 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

45~48 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

49~52 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

53~56 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

57~60 2.625 2.75 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

61~64 2.75 2.875 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

65~68 3 3 3 3.125 3.125 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

69~72 3.125 3.125 3.125 3.125 3.25 3.25 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

73~76 3.25 3.25 3.25 3.25 3.375 3.375 3.375 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

77~80 3.375 3.375 3.375 3.5 3.5 3.5 3.5 3.625 3.625 3.875 4 4.125 4.25 4.375 4.5

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

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

121~140 5.25 5.375 5.5 5.5 5.5 5.5 5.5 5.5 5.5 5.5 5.5 5.625 5.625 5.625 5.625

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

161~200 6.25 6.375 6.5 6.625 6.75 6.875 7 7.125 7.25 7.375 7.5 7.625 7.75 7.875 8

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



91 (128)))




HSUPA data UEs

per HSUPA

scheduler


49.2 50.7 52.2 53.6 55.0 56.5 58 59.4 60.9 62.35 63.8 65.25 66.7 68.1 69.6






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

11~12 2.875 3.125 3.125 3.125 3.375 3.375 3.375 3.5 3.625 3.625 3.625 3.875 3.875 4 4

13~14 2.875 3.125 3.125 3.125 3.375 3.375 3.375 3.5 3.625 3.625 3.625 3.875 3.875 4 4

15~16 2.875 3.125 3.125 3.125 3.375 3.375 3.375 3.5 3.625 3.625 3.625 3.875 3.875 4 4

17~18 2.875 3.125 3.125 3.125 3.375 3.375 3.375 3.5 3.625 3.625 3.625 3.875 4.125 4.25 4.25

19~20 3.25 3.25 3.25 3.25 3.375 3.375 3.375 3.5 3.625 3.625 3.625 3.875 4.125 4.25 4.25

21~22 3.625 3.625 3.625 3.625 3.625 3.625 3.625 3.625 3.625 3.75 3.75 3.875 4.125 4.25 4.25

23~24 4 4 4 4 4 4 4 4 4 4 4 4 4.125 4.25 4.25

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

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

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

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

33~34 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.5 5.5 5.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.875 5.875 5.875 5.875 5.875

37~38 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.25

39~40 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5


DN0981084 Issue 02D


DND 92 (128)))


HSUPA data UEs

per HSUPA scheduler


49.2 50.7 52.2 53.6 55.0 56.5 58 59.4 60.9 62.35 63.8 65.25 66.7 68.1 69.6

41~44 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5

45~48 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5

49~52 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5

53~56 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5

57~60 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5

61~64 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5

65~68 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5

69~72 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5

73~76 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5

77~80 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5

81~100 4.625 4.75 4.875 5 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5

101~120 5.125 5.25 5.25 5.25 5.25 5.25 5.5 5.5 5.75 5.875 5.875 6 6.25 6.25 6.5

121~140 5.625 5.75 5.75 5.75 5.75 5.875 5.875 5.875 5.875 5.875 6 6 6.25 6.25 6.5

141~160 6.75 6.75 6.75 6.75 6.75 6.75 6.75 6.75 6.75 6.75 6.875 6.875 6.875 6.875 6.875

161~200 8.125 8.375 8.5 8.5 8.5 8.5 8.5 8.5 8.5 8.5 8.5 8.5 8.5 8.5 8.5

201~240 8.875 9 9.125 9.25 9.375 9.5 9.625 9.75 10 10.125 10.125 10.125 10.125 10.125 10.125



93 (128)))



When HSUPA 16QAM is in use, one UE transmitting with 16QAM modulation requires one subunit form System Module Rel.2.

Note that subunit utilization might change on TTI base. In one TTI, single UE transmits with 16QAM modulation. While in the second TTI different modulation can be used depending on, for example, radio conditions or amount of data in the UE buffer.

A single user cannot exceed the limit of one subunit with 11 Mbps (16QAM). Only one 16QAM transmitting user can be located in the given subunit (TTI) per cell.

No more than 15 subunits can be allocated for HSUPA per single System Module Rel.2 and 16.875 subunits per System Module Rel.3

LCG configuration type FSMF FSMF + FBBA FSMF + 2xFBBA

Small HSPA 4.875 10.875 16.875

Normal HSPA 4.375 10.375 16.575

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

If more than 240 HSUPA users per single System Module Rel.2 are required, then the second LCG has to be created.

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

To calculate the subunits reservation inside Rel.2 or Rel.3 System Module for mixed user type case, (F-DPCH/no-FDPCH/2ms TTI/10msTTI users, 16QAM transmitting users (System Module rel.2) and CS Voice over HSPA), the following 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 + 16QAM_2msTTI_Subunits +

CS_Voice_over _HSPA_Subunits

Equation 8 HSUPA subunits formula

where:

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

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


DN0981084 Issue 02D


DND 94 (128)))

No-F-DPCH_2msTTI_Subunits – subunits required for HSUPA no-F-DPCH 2ms TTI users, calculated from Table 23 and Table 29;

No-F-DPCH_10msTTI_Subunits – subunits required for HSUPA no-F-DPCH 10ms TTI users, calculated from Table 25 and Table 27;

16QAM_2msTTI_Subunits – subunits required for UEs simultaneously transmitting with 16QAM modulation (note that only UE in good radio condition and appropriate amount of data in buffer is able to use 16QAM transmission).

CS_Voice_over_HSPA_Subunits – subunits required for CS Voice over HSPA users.

For example:

System Module Rel.2 in use;

HSUPA BTS combined L1 throughput = 39Mbps;

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 7Mbps throughput;

Number of 16QAM 2ms TTI users = 1 UEs with 11Mbps throughput.

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

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

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

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

16QAM_2msTTI_Subunits – one subunit required (1 user * 1 subunit = 1 subunit).

According to

Equation 8: HSUPA_subunits = 1.5 + 1.5 + 2 + 2.5 + 1 = 8.5

Therefore: 8.5 subunits for HSUPA users are required.

The HSUPA resource allocation tables presented above define the minimum amount of baseband resources needed to support certain number of users with the defined L1 throughput. However if BTS contains available baseband resources (i.e. resources not currently allocated for Rel99 or HSPA) the HSUPA baseband resources consumption is typically higher, in order to fully utilize the fast scheduling capabilities of HSUPA packet scheduler, improve UE Round Trip Time, UE instantaneous throughput and to support the bursty nature of E-DCH traffic. Therefore subunits utilization indicators may appear



95 (128)))



high but this does not necessarily indicate that the Flexi BTS baseband resources have reached maximum capacity. The dynamic allocation of baseband resources keeps the HSUPA subunits utilization on a high percent level although more calls can be served additionally.

By allocating extra (not used) subunits for the users, the scheduling changes are much faster (in scale of scheduling periods) as there is no immediate need for HW allocation changes and the new serving grants can be provided to the UEs immediately.

For information about capacity and usage monitoring please refer to Managing WCDMA RAN Capacity document.

4.1.5 Static HSUPA resources allocation

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

The BTS reserves the minimum capacity for HSUPA based on commissioning

parameters HSUPA BB decoding capacity Mbps and HSUPA BB minimum users.

The value for HSUPA BB decoding capacity Mbps refers to the static commissioned

minimum reservation for baseband L1 throughput.

HSUPA UEs per HSUPA scheduler


<1.4 1.4 2.8 4.2 5.6

1 0.125 0.25 0.375 0.375 0.375

2 0.125 0.25 0.375 0.625 0.625

3-4 0.25 0.25 0.375 0.625 0.625

5-6 0.25 0.25 0.375 0.625 0.625

7-8 0.375 0.375 0.5 0.625 0.625

9-10 0.375 0.375 0.5 0.625 0.625

11-12 0.375 0.375 0.5 0.75 0.75

13-14 0.375 0.375 0.625 0.75 0.75

15-16 0.5 0.5 0.625 0.75 0.875


DN0981084 Issue 02D


DND 96 (128)))

17-18 0.5 0.5 0.625 0.875 0.875

19-20 0.5 0.5 0.75 0.875 1

21-22 0.625 0.625 0.75 0.875 1

23-24 0.625 0.625 0.75 1 1

Table 31 HSUPA static resources allocation for System Module rel.3

HSUPA throughput may be bigger if there is more capacity available in the BTS.

If the operator maps HSPA frequencies to different System Modules, the BTS reserves the minimum capacity for HSUPA only for one System Module based on the commissioning parameters.

4.1.6 Interference Cancellation unit (PIC pool)

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

PIC pool unit is System Module and LCG specific therefore it can provide interference cancelation for HSUPA cells dedicated to LCG and System Module where PIC pool unit and HSPA schedulers’ resources (HSUPA scheduler and HSDPA scheduler) have been allocated.

Interference Cancellation unit (PIC pool) with System Module Rel.2

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

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

One PIC pool unit consumes one subunit capacity.

The table below contains summary information related to System Module Rel.2 PIC pool unit.

PIC pool unit parameters

2 way Rx diversity

Max number of cells supported by single PIC pool unit 6



97 (128)))



Max number of cells with simultaneous interference cancellation performed by

single PIC pool unit 2

Max number of PIC pools per System Module rel.2 2

Table 32 System Module rel.2 PIC pool unit summary information

Figure 22 Exemplary BTS configuration, two System Modules Rel.2, sector based pooling used (2 LCGs), 3 PIC pools activated

Interference Cancellation unit (PIC pool) with System Module Rel.3

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

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

One PIC pool unit consumes one subunit capacity.

Table below contains summary information related to System Module Rel.3 PIC pool unit.

PIC pool unit parameters

2 way Rx diversity

Max number of cells supported by single PIC pool unit 6

Max number of cells with simultaneous interference cancellation performed by

single PIC pool unit 6


DN0981084 Issue 02D


DND 98 (128)))

Max number of PIC pools per System Module rel.3

2

Table 33 System Module rel.3 PIC pool unit summary information

Figure 23 Exemplary BTS configuration, one System Module Rel.3, one LCG, 2 PIC pools activated (interference cancellation in all cells at the same time – 2way Rx Div assumed)

4.1.7 HS Cell_FACH users

HS-FACH feature allows sending and receiving small packet of data Cell_FACH state using transmission on HSUPA and HSDPA channels (UL/DL). Cell_FACH users do not require any capacity license (HSDPA/HSUPA Processing Set / Rel.99 CE license).

However for handling HS-Cell_FACH users, dedicated baseband resource are required.

Using Min number of HS-FACH users parameter operator can commission static

resources for Cell_FACH users. Reservation is done in the steps (four steps available) for each LCG. Single step provides baseband capacity for 10 HS-FACH users (in maximum 40 HS-FACH users can be served in LCG)

Note that HS-FACH DL users does not require any baseband reservation.



99 (128)))



HS_FACH System Module Rel.2

HS-FACH users step baseband capacity

reservation 0.25 subunit

Table 34 HS-FACH users baseband requirements

Min number of HS-FACH users parameter has default value “0”, which means that

no static allocation is done and dynamically 1 HSUPA Resources Step can be allocated for HS-Cell_FACH users (supporting max 10 users)

HS-Cell_FACH user is treated as normal HSUPA user with respect to maximum number of users supported by HSDPA and HSUPA schedulers.

For example:

One HSUPA and HSDPA scheduler,

System Module rel.2,

Max amount of supported HSUPA users per scheduler = 240 users; max amount of HSDPA users per scheduler = 240 users

Two HS Cell_FACH users available,

238 HSUPA users can be still supported by HSUPA scheduler.

238 HSDPA users can be still supported by HSDPA scheduler.

4.1.8 CS Voice over HSPA users allocation

CS Voice over HSPA users consumes subunits capacity. With System Module Rel.2 up to 18 CS Voice over HSPA users can be allocated in one Subunit.

Number of CS Voice over HSPA users

Subunit (System Module Rel.2)

4 0.25

9 0.5

13 0.75

18 1 Table 35 CS Voice over HSPA users (System Module Rel.2)


DN0981084 Issue 02D


DND 100 (128)))

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

subunit.

Number of CS Voice over HSPA users

Subunit (System Module 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 36 CS Voice over HSPA users (System Module Rel.3)

NOTE: CS voice over HSPA users does not consume Rel99 CE licenses.

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 the HSUPA license (HSUPA processing set) and the HSDPA license (HSDPA processing set).

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: CS Voice over HSPA feature description.

4.1.9 HSUPA BTS Processing Set resources allocation

If one LCG has baseband resources from two System Modules, the BTS will allocate the licensed HSUPA capacity to same System Module where an HSUPA scheduler exists. If the HSUPA scheduler is present in both System Modules, BTS will allocate HSUPA licenses proportionally to baseband capacity for traffic use of each System Module. The sum of HSUPA licenses allocated to both HSUPA schedulers is always equal to total available BB resources required to reach the licensed number of users and licensed throughput.



101 (128)))



Each HSUPA BTS processing set license increases the LCG’s maximum user amount by twenty four users and the available throughput by 5.8Mbps. For example, if two HSUPA BTS processing sets were bought, then up to 2x5.8Mbps = 11.6Mbps throughput will be supported and up to 2x24 users = 48 users. Note that also an ASW license might be needed to reach a certain throughput.

In rare case with only one HSUPA PS license and without any Rel.99 CE licenses, the maximum number of HSUPA licensed users in LCG may not be achieved (depending on HSUPA user type mix 2ms/10ms/FDPCH/non-FDPCH). This is because in the considered case, one HSUPA resource step (equivalent of 12 Rel.99 CEs) is reserved for Rel.99 users, as each user entering the network is configured to Rel.99 bearer and only after is reconfigured to HSUPA bearer. When at least 12 Rel.99 licenses are purchased, one HSUPA PS license always assures up to 24 HSUPA licensed users in LCG.

In WN8.0, the HSUPA BTS Processing Set allows to reach up to 5.8Mbps throughput and up to 24 users simultaneously. To calculate the required number of HSUPA BTS processing sets, it is recommended to use the following formula:

Number_of_HSUPA_BTS_Processing_Sets = max {

Roundup (HSUPA_users / 24); Roundup (HSUPA_data_users_throughput / 5.8) };

Equation 9 Number of HSUPA BTS Processing Sets for HSUPA users

where:

HSUPA_users – is the number of HSUPA users (data + CS Voice over HSPA users)

HSUPA_data_users_throughput – is combined HSUPA throughput (data + CS Voice over HSPA users) referred in Mbps.

Exemplary calculation of required number of HSUPA Processing Sets with System Module Rel.2:

After baseband dimensioning (done using

Equation 8, for more information see previous example) it occurs that 8.5 subunits in total are required for HSUPA (data) users (83 HSUPA data users/combined L1 throughput = 39Mbps);

Using Equation 9: Number of HSUPA BTS Processing Sets = max (roundup (83 / 24) ; roundup(39 / 5,8) ) = max ( roundup(3,45); roundup(6,7) ) = max( 4 ; 7) = 7;

The required throughput and number of active HSUPA users can be achieved simultaneously. Also, the maximum number of allocated subunits is not equal to available HSUPA BTS processing sets, as shown in this example.

If Baseband pooling is used then BTS will divide the HSUPA licenses between LCGs

according to the commissioned share (shareOfHSUPALicences). The sum of LCG


DN0981084 Issue 02D


DND 102 (128)))

shares is always 100%. HSUPA license share is performed with HSUPA BTS processing set license granularity. If licenses cannot be shared equally between LCGs, the BTS will divide 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.

Extended cell in Flexi BTS


103 (128)))



5 Extended cell in Flexi BTS

The 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 is needed to calculate 1* 20km cell according to normal common channel dimensioning rules 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 be configured 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 are as follows:

Required baseband resources in case of Flexi System Module Rel. 2:

The number of baseband resources (CCCH pools) required for the Extended Cell depends on cell range and site configuration. One Extended Cell with range up to 180km can be served with CCCH pool (one subunit). However, if a lower cell radius is required, more than one Extended Cell can be served with one CCCH pool or the Extended Cell can be served together with normal cells using CCCH pool included in the System Module Rel.2 capacity. Note that each CCCH pool requires CCCH license for activation.

For example:

1+1/10km + 1/40km (2way Rx div) – 1 CCCH pool (48 Re99 CE license) required for CCCH

Dimensioning WCDMA RAN: Flexi BTS Baseband Extended cell in Flexi BTS

DN0981084 Issue 02D


DND 104 (128)))

2+2/10km + 2/40km (2way Rx div) – 1 CCCH pool (48 Re99 CE license) required for CCCH

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

cellsof

i

__#

1

ii 480 Rx) * Signatures of # * Range (Cell

where:

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

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

# of Signatures - means the 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} in case of 4 way Rx diversity Rx= 4, otherwise Rx =2

Required baseband resources in case of Flexi System Module Rel. 3:

The number of baseband resources (CCCH pools) required for the Extended Cell depends on cell range and site configuration. One Extended Cell with range up to 180km can 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 Cell can be served together with normal cells using CCCH resources included in the System Module Rel.3 capacity. Note that each CCCH pool requires CCCH Processing Set for activation.

For example:

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

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

Extended cell in Flexi BTS


105 (128)))



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

cellsof

i

__#

1


where:

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

Cell range – user cell radius stated in kilometers (rounded up to the whole kilometer 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:





Dimensioning WCDMA RAN: Flexi BTS Baseband WCDMA BTS capacity allocation principles

DN0981084 Issue 02D


DND 106 (128)))

6 WCDMA BTS capacity allocation principles

This chapter describes baseband allocation details for System Module rel.3 and System Module rel.2

6.1 System Module rel.3 capacity details

Table 4 and Table 5 presents HSDPA scheduler baseband consumption for typical configurations. HSDPA scheduler baseband resources required for any configuration can be calculated using formulas presented below.

Equation 10:

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

Equation 10 HSDPA subunits requirement (Small HSPA or Normal HSPA configuration

where:

Min_HSDPA_subunits = minimum number of LCG configuration subunits requirements from Table 37

Cells_factor = factor calculated according to Equation 11

Note that HSDPA_subunits describes baseband resources responsible for HSDPA scheduler(s). In addition to HSDPA baseband resources HSDPA subunits offer certain amount of CCCH baseband processing resources (for more information, see chapter 2.5.1).

Equation 11:

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

Equation 11 LCG cells factor

WCDMA BTS capacity allocation principles


107 (128)))



where:

non_MIMO_cells = number of non-MIMO and non-VAM cells in LCG (sum of Rel.99 only and HSPA cells);

MIMO_cells = number of HSPA MIMO or non-MIMO but VAM cells in LCG.

The table below presents the minimum number of LCG configuration subunits.

LCG configuration

type

Minimum number of HSDPA subunits (Min_HSDPA_subunits)

Small HSPA 0.5

Normal HSPA 1

Table 37 Minimum HSDPA subunits requirement

For example:

1) Scenario assumptions:

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

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

10km cell range/2 way Rx Div;

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 available the whole System Module Rel.3 baseband capacity (5.5 subunits) is available (dedicated) for LCG

LCG_pure_traffic_subunits = LCG_dedicated_subunits – Additional_CCCH_subunits – PIC_pool_subunits – HSDPA_subunits = 5.5 – 0 – 1 – 1.625 = 2.875


DN0981084 Issue 02D


DND 108 (128)))

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

The LCG pure traffic capacity is 2.875 subunits.

2) Scenario assumptions:

FSMF + FBBA / 11.5 subunits (2 LCGs: 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 HSPA cells)) / 3 subunits dedicated;

10km cell range/2 way Rx Div;

VAM not used;

Interference cancellation for 12 cells/LCG1 (2 PIC pools configured).

LCG1 pure traffic capacity calculation:

Cells_factor = Roundup{ (Roundup (non_MIMO_cells/3) + MIMO_cells ) / 2 } = 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 by resources included in SM Rel.3 capacity. Remaining 6 cells/10km/2way Rx Div are processed with resources included in HSDPA scheduler subunits capacity (1x CCCH Processing Set licenses needed)

According to scenario assumptions during BTS commissioning 8.5 subunits were 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

The LCG1 pure traffic capacity is 5.375 subunit.



109 (128)))



LCG2 pure traffic capacity calculation:


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 (1x CCCH Processing Set license required). Note that any additional CCCH processing (for example, in extended cell range case) can be done with baseband resources included in HSDPA scheduler subunits capacity (CCCH Processing Set license required)

According to scenario assumptions during BTS commissioning 3 subunits were dedicated 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

The LCG2 pure traffic capacity is 1.875.

6.2 System Module rel.2 capacity details

The maximum available baseband capacity of Flexi Multimode BTS System Modules (FSMC, FSMD, and FSME) for R99 and HSUPA traffic depends on:

Number of commissioned cells;

CCCH processing subunits that need to be licensed for SM Rel.2 capacity;

HSDPA scheduler subunits;

Number of activated Interference Cancellation units (PIC pools)

HS-Cell_FACH users subunits

HSUPA static allocation subunits

The available Rel99 CE capacity can be calculated using the formula below:

System Module_Rel99_CE_capacity = min (#Rel99_CE_licenses; (Rel99_CE_Subunit_capacity * number_of_available_subunits)

Equation 12 System Module R99 CE capacity


DN0981084 Issue 02D


DND 110 (128)))

where:

#Rel99_CE_licenses = number of available Rel99 CE licenses;

Rel99_CE_subunit_capacity = Rel99 CE subunit capacity (48 Rel99 CE);

number_of_available_subunits = number of subunits not allocated for CCCH processing, HSDPA processing or interference cancellation. The number of available subunits can be calculated according to formula below.

Number_of available_subunits = (number_of_subunits – subunits_for HSDPA – subunits_for_PIC_pool – subunits_for_static_HSUPA)

Equation 13 Number of available subunits

where:

number of subunits = number of System Module Rel.2 subunits from Table 3.

subunits_for_HSDPA = number of HSDPA commissioned subunits;

subunits_for_PIC_pool =number of commissioned interference cancellation subunits;

subunits_for_static_HSUPA - number of HSUPA static commissioned subunits.

6.3 CCCH baseband resources allocation details

Each LCG requires own resources for CCCH processing according to dedicated amount of cells, cells range and Rx div type.

In case if LCG covers more than one System Module CCCH processing resources might be allocated at Master or Extension System Module or both System Modules.

Baseband resource allocation for CCCH processing can be influenced by ‘Frequency layer mapping to System Modules.

NOTE:

Frequency layer mapping to HW (System Module) is optional

Frequency layer mapping to HW (System Module) requires two System Modules.

Frequency mapping to HW is allowed with only one LCG per BTS

With commissioning parameter Mapping HSPA Cell to HW, the operator can map

frequency layers to different System Modules (at least one System Module Rel.2 is required). Some frequencies can be mapped to one System Module and other frequencies to another System Module.



111 (128)))



If some frequency layer is mapped to a System Module, the selected System Module has to provide Common Control Channels, HSUPA, and HSDPA processing resources (including A-DCH and SRB resources) for cells from the assigned frequency layer. In this case, DCH users from the assigned frequency layer are also allocated at the selected System Module. However, when the full System Module capacity is occupied, new DCH users can be allocated at the second System Module.

Figure 24 Frequency layers mapping to HW exemplary configuration (FSME+ FSMD)

If the frequency mapping is used, the selected System Module has to provide baseband resources for CCCH processing according to the number of cells mapped to the System Module.

For example:

Site with two carriers (for example 2+2+2 /20km) and Flexi WBTS FSME+FSMD Frequency layer #1 is mapped to FSMF (1+1+1) – 0 Rel99 CE for CCCH processing required (CCCH processing for 1+1+1/20km included in FSME System Module capacity).

Frequency layer #2 is mapped to FSMD (1+1+1) – 0 Rel99 CE for CCCH processing required (CCCH processing for 1+1+1/20km included in System Module Rel.2 capacity).

If frequency mapping is not used and one LCG created HSPA (HSUPA scheduler, HSDPA scheduler, A-DCH and SRB resources) is allocated on single System Module.

Table 38 presents the required Rel99 CE capacity that need to be licensed for the FSMC/D/E + FSMC/D/E configuration, and cell range up to 10km (2 way Rx Div) when frequency layer mapping is used.


DN0981084 Issue 02D


DND 112 (128)))

Number of cells Number of LCG

CCCH Processing Sets licensed at

FSMC/D/E

CCCH Processing Sets licensed at

FSMF/FBBA

1…3 (for example 1+1+1) 1 LCG 0

0* Rel99 CE (1+1+1, carrier 1 mapped to Extension Module or

frequency layer mapping not used)

1…3 (for example 1+1+1) 1 LCG

0* Rel99 CE

(1+1+1, carrier 1 mapped to Master

Module)

0

4…6 (for example 2+2+2) 1 LCG 0

0* Rel99 CE

(2+2+2, carrier 1 and 2 mapped to Extension Module or frequency

layer mapping not used)

4…6 (for example 2+2+2) 1 LCG

0* Rel99 CE

(1+1+1, carrier 1 mapped to Master

Module)

0* Rel99 CE

(1+1+1, carrier 2 mapped to Extension

Module)

Table 38 CCCH Processing Sets for FSMF + FSMC/D/E configuration and cell range <10km using “Mapping HSPA Cell to HW” commissioning parameter

6.4 CCCH baseband resources allocation for SM rel.3 details

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

cellsof

i

__#

1


where:

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

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

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

where:



113 (128)))



2-way Rx div:




4-way Rx div:





For example:

1) FSMF, 1 LCG - R99 only configuration, 12 cells/10km cell range, 2 way 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 cell range, 2 way Rx Div. - 0 x CCCH Processing Set (CCCH pool included in System Module capacity) required for 6 cells - 1 x CCCH Processing Set required for 6 cells

NOTE:

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

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

Equation 3:

Number_of_additional_CCCH_pools =

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

Equation 14 Number of LCG available CCCH processing resources

where:


DN0981084 Issue 02D


DND 114 (128)))

Min_HSDPA_subunits - Minimum number of HSDPA subunits from Table 37.

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.99 only cells + 3 HSPA non-MIMO and non-VAM cells));


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



115 (128)))



6.5 CCCH baseband resources allocation for SM rel.2 details

Number of cells that can be served with one CCCH pool from System Module Rel.2 can be determined with the formula below:

cellsof

i

__#

1


where:

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

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

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

where:

2-way Rx div:




4-way Rx div:





6.6 Local Cell Grouping details

In case BTS with more than one LCG and two System Modules rel.2, BTS tries to allocate whole LCG baseband capacity to one System Module. Therefore LCG with the biggest amount of dedicated resources is allocated to System Module with the biggest capacity. The LCG having the next biggest amount of resources is allocated to System Module with the biggest available capacity. This is repeated for all remaining LCGs.

For details of HSDPA resources allocation, see chapter 3


DN0981084 Issue 02D


DND 116 (128)))

General rules of Baseband HW commissioning with two System Modules:

1) In case of two LCGs, LCG having bigger amount of HW resources commissioned ("Max. HW BB capacity") is allocated to System Module that has bigger capacity (e.g. FSME has bigger capacity as FSMD) or is shared on both System Modules. If both System Modules have the same capacity (for example Master FSME + Extension FSME), LCG having bigger amount of HW resources commissioned covers capacity of whole Master FSME and part of the capacity of Extension FSME.

LCG having smaller amount of HW resources commissioned is allocated to FSM that has smaller capacity or is shared on both System Modules. For example in case of Master FSME + Extension FSMC, LCG with smaller amount of HW resources commissioned gets capacity of:

- whole FSMC

- or whole FSMC and part of FSME.

2) In case of two LCGs, if Access Baseband Capacity=50% and total number of

Subunits is divisible by two, LCG with lower ID (LCG#1 has lower ID than LCG#2) is allocated to System Module with bigger capacity while LCG with higher ID is shared on both System Modules.

In case both System Modules have the same capacity, LCG with lower ID is allocated to Master System Module while LCG with higher ID is allocated to Extension System Module

For example:

Two LCGs with 50% share of BTS resources. BTS configuration with even number of subunits in BTS: FSMC+FSME.

As a result, both LCGs have the same amount of subunits per FSM.

o LCG with lower ID (LCG#1) is allocated to FSM with bigger capacity (FSME)

o LCG with higher ID (LCG#2) is shared on FSME and FSMC

3) If Access Baseband Capacity=50% and total number of Subunits is not divisible

by two, LCG with higher ID gets one Subunit more and rule from point 1) is applied.

For example:

Two LCGs with 50% share of BTS resources. BTS configuration with odd number of Subunits in BTS: FSME+FSMD.



117 (128)))



As a result, LCG with higher ID gets one SU more than LCG with lower ID and is allocated on FSM with bigger capacity:

o 16SU is allocated to LCG#2 on FSME;

o 15SU is allocated to LCG#1 shared on FSME and FSMD.

4) In case BTS with more than two LCGs, after allocating LCG#1 and LCG#2, BTS allocates 3

rd and 4

th LCG with respect to rule:

LCG with bigger amount of HW resources is allocated to System Modules where LCG in question has more resources. In case LCG has equal share of resources on both System Modules, LCG is allocated on Master System Module.

Note that Subunits of the BTS are dedicated to LCGs according to Access Baseband

Capacity commissioning parameter but the final System Module Rel.2 and LCG

Subunits capacity depends on number of cells as specified in chapter 2.3

For example:

12 cells per BTS.

a) One LCG:

FSME FSME

12 cells are served by LCG

As a result, 2x16 SU available for traffic use (CCCH resources included in two SM Rel.2)

b) Two LCGs, six cells per LCG:

FSME FSME

6 cells are served

by LCG1

6 cells are served

by LCG2

As a result, 2x18 SU available for traffic use (CCCH resources included in two SM Rel.2)

c) Two LCGs, 9 cells +3 cells:


DN0981084 Issue 02D


DND 118 (128)))

SM#1 serves 9 cells

from LCG1

SM#2 serves 9 cells

from LCG1 and 3

cells from LCG2

FSME FSME

9 cells are served by

LCG1

3 cells are

served by LCG2

As a result, 17 SU + 16 SU are available. 48 R99 CE licenses for CCCH processing are required for LCG1, thus 16SU + 16SU available for traffic use.

In case HSUPA Interference Cancellation Receiver (RAN1302) is used, LCGs are created according to the following rules:

1) BTS with one System Module, maximum one LCG containing PIC pool units can be created;

2) BTS with two System Modules, maximum two LCGs each containing PIC pool units can be created);

For example:

FSMD+FSME / 3+3+3 (9 cells);

LCG1:80% (6 cells, Interference Cancellation (PIC)), LCG2:20% (3 cells, Interference Cancellation (PIC));

FSMD FSME

PIC

LCG 2 LCG 1 LCG 1

PIC PIC

Figure 25 Example of LCG configuration with Interference Cancellation

For HSUPA Interference Cancellation Receiver details, see chapter 4.1.6

Rel99 CE license capacity

For dedicating the Rel99 CE license capacity usage between the operators in MORAN case, it is possible to define in commissioning the dedicated license capacity

(Dedicated BaseBand capacity parameter), which is optional. With this allocation

the operator can allocate to LCG a guaranteed number of Rel99 CE licenses. It is possible to guarantee, for example, 20% of licenses to operator#1 (LCG#1) and operator#2 (LCG#2), and then 60% of licenses are in use by both operators (common Rel99 CE license pool).



119 (128)))



It is also possible to use dedicatedel99 CE license capacity in the single operator case (if more than one LCG is available), for example, if the operator wants to prioritize traffic from certain carrier(s) (LCG).

For example:

a) Site with two carriers (2+2+2) is shared by two operators. Site configuration is:

FSMD + FSMD (2 LCG), 500 Rel99 CE licences;

b) Site with three carriers (3+3+3) is shared by two operators (operator #1 - 1+1+1,

operator #2 – 2+2+2)

FSME (2LCG) 500 Rel99 CE licences ;

For all cases, both operators agreed to share Rel99 CE licenses 20% to 40% as the dedicated capacity and the rest as common capacity.

Figure 26 Example of MORAN case – Flexi FSMD + FSMD

In case b) 100 Rel99 CE licenses (20%) are dedicated to LCG#1 (operator #1) and 200 Rel99 CE licenses (40%) are dedicated to LCG#2 (operator #2) and the rest of the available CE Rel99 licenses – 200 (40%) can be shared by both LCGs (can be accessed by both operators on a first come – first served principle). Because System Module Rel.2 is used (as well as RF modules) the BB capacity can be freely divided between the operators. In the example, LCG#1 (operator #1) has the capacity of 288 Rel99 CE and LCG#2 (operator #2) has the capacity of 528 Rel99 CE (HSDPA activated).


DN0981084 Issue 02D


DND 120 (128)))

Figure 27 Example of MORAN case – Flexi FSME

For more detailed information about Local Cell Grouping, see Flexi WCDMA BTS Commissioning.



121 (128)))



6.7 Allocation of Dedicated Channels

With Mapping HSPA Cell to HW commissioning parameter operator can map HSPA

frequency layers to different System Modules (note that mapping of frequency layers to HW is not mandatory).

If a frequency layer is mapped to a given System Module, the selected System Module has to provide resources for Common Control Channels (as well as HSPA resources) for cells from the assigned frequency layer. In this case, DCH users from the assigned frequency layer are allocated at the selected System Module. If the selected System Module is not able to allocate more DCH users from the assigned frequency layer, new DCH users can be allocated at a different System

6.8 HSDPA allocation principles

In case of two System Modules Rel.2, one LCG and HSPA frequency layer mapping is not used, HSDPA schedulers can be activated only at one System Module, allowing maximum of two HSDPA schedulers per BTS.

For BTS configuration with two System Modules Rel.2 and more than one LCG, HSDPA resources are allocated to particular System Modules depending on LCG configuration. To know the HSDPA allocation to particular System Module, see chapters indicated below:

Fixed LCGs (chapter 6.8.1);

Flexible LCG. In this case, HSDPA allocation also depends on whether Maximum Throughput per HSDPA Scheduler is commissioned on:

o Both System Modules (chapter 1.3.5.2);

o One of the two System Modules 6.8.3);

o None of the System Modules 6.8.4).

For the LCG allocation rules in BTS configuration with two System Modules, see chapter 6.6


DN0981084 Issue 02D


DND 122 (128)))

6.8.1 Fixed LCGs

If baseband capacity is shared between LCGs according to System Module capacity (fixed LCGs), HSDPA resources of particular LCG is allocated according to rule:

The HSDPA resources of LCG#1 are allocated to Master System Module while HSDPA resources of LCG#2 are allocated to Extension System Module.

NOTE:

Exception is 3+3+3 B-type configuration. In this case HSDPA of LCG having one frequency layer is allocated to Master System Module while HSDPA of LCG having two frequency layers is allocated to Extension System Module.

6.8.2 Flexible LCG. Maximum Throughput per HSDPA Scheduler commissioned on both System Modules

In case of flexible LCGs and HSDPA Throughput Step > 0 on both System Modules

general rules of HSDPA allocation are as follows:

1) HSDPA of LCG having the biggest amount of commissioned BB HW resources

(Access Baseband Capacity) is allocated only to System Module with bigger

capacity.

HSDPA of LCG with the next biggest amount of resources is allocated only to System Module with smaller capacity (See below Example a)).

In case both System Modules have equal capacity (for example FSMD+FSMD), HSDPA of LCG having the biggest amount of resources is allocated only to Master System Module. HSDPA of LCG having the next biggest amount of resources is allocated only to Extension System Module.

2) In case two LCGs, if both LCGs have the same share of BTS baseband resources

(Access Baseband Capacity=50%) LCG allocation to particular System Module

depends on whether BTS has even or odd number of Subunits (see chapter 1.2.2.5 for details).

a) Even number of Subunits:

HSDPA of LCG#1 is allocated only to System Module with bigger capacity. HSDPA of LCG#2 is allocated only to System Module with smaller capacity (see below Example b)).

If both System Modules have equal capacity (for example, FSMD+FSMD), HSDPA of LCG#1 is allocated only to Master System Module. HSDPA of LCG#2 is allocated only to Extension System Module.

b) Odd number of Subunits:



123 (128)))



HSDPA of LCG#2 is allocated only to System Module with bigger capacity. HSDPA of LCG#1 is allocated only to System Module with smaller capacity (see below Example c)).

If both System Modules have equal capacity (for example FSMD+FSMD), HSDPA of LCG#2 is allocated only to Master System Module. HSDPA of LCG#1 is allocated only to Extension System Module.

3) After allocating HSDPA of LCG#1 and LCG#2, BTS allocates HSDPA of 3rd

and 4th

LCG with respect to rule:

Bigger LCG or LCG with lower ID is allocated first. In case LCG has resources on both System Modules, HSDPA is allocated only to System Module where LCG in question has more resources. In case LCG has equal share of resources on both System Modules, HSDPA is allocated only to Master System Module.

Example a):

LCG#1=80%, LCG#2=20%. BTS configuration: FSMD (Master SM) + FSME (Extension SM).

As a result, HSDPA of LCG with bigger amount of commissioned resources (LCG#1) is allocated only to System Module with bigger capacity (FSME). HSDPA of LCG with smaller amount of commissioned resources (LCG#2) is allocated to FSMD.

LCG#2

FSME

HSDPA LCG#1

LCG#1

FSMD

HSDPA LCG#2

Table 39 FSMD+FSME, LCG share 80% / 20%; HSDPA of LCG with more resources (LCG#1) is allocated to System Module with bigger capacity (FSME).

Example b):

Two LCGs with 50% share of BTS resources and even number of Subunits in BTS. BTS configuration: FSMC + FSME.

Both LCGs have the same amount of resources. Thus, HSDPA of LCG with lower index (LCG#1) is allocated to System Module with bigger capacity (FSME). LCG#2 is allocated only to other System Module (FSMC).

LCG#2

FSME

HSDPA LCG#1

LCG#1

FSMC

HSDPA LCG#2

Table 40 FSMC+FSME, 50% LCG share, even number of subunits. HSDPA of LCG#1 is allocated only to System Module with bigger capacity (FSME).


DN0981084 Issue 02D


DND 124 (128)))

Example c):

Two LCGs with 50% share of BTS resources and odd number of Subunits in BTS. BTS configuration: FSME + FSMD:

LCG with higher ID (LCG#2) gets one Subunit more than LCG with lower ID (LCG#1). HSDPA of LCG with bigger amount of resources (LCG#2) is allocated only to System Module with bigger capacity (FSME). HSDPA of LCG#1 is allocated only to other System Module (FSMD).

LCG#1

FSME

HSDPA LCG#2

LCG#2

FSMD

HSDPA LCG#1

Table 41 FSMD+FSME, 50% LCG share, odd number of subunits. HSDPA of LCG#2 is allocated only to System Module bigger capacity (FSME).

6.8.3 Maximum Throughput per HSDPA Scheduler commissioned on one of the two System Modules

In case of Flexible LCGs and HSDPA Throughput Step > 0 on one of the two System

Modules general rules of HSDPA allocation are as follows:

1) LCG with resources shared on both System Modules has HSDPA allocated only to System Module with Maximum Throughput per HSDPA Scheduler commissioned;

2) LCG with resources only on System Module with not commissioned “Maximum Throughput per HSDPA Scheduler” has HSDPA allocated according to Table 15

6.8.4 Maximum Throughput per HSDPA Scheduler not commissioned on any of the two System Modules

In case of Flexible LCGs and HSDPA Throughput Step is not selected the HSDPA

allocation rules are as follows:

Rules 1), 2) and 3) from 6.8.2 apply. HSDPA is allocated according to Table 15



125 (128)))



6.9 E-TFCI table selection

E-DCH Transport Format Combination Indicator (E-TFCI) corresponds to single Transport Block 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 3GPP defines two E-TFCI tables:

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

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

In case of low data rates (single Mac-d PDU) and E-TFCI Table 0, the smallest physical channel for sending one MAC-d PDU in a TTI is limited to Spreading Factor 16 (SF16). It is limited by coding rate, which has constant threshold value in 3GPP. E-TFCI Table 1 allows usage of physical channel SF32. Physical channel SF16 requires roughly double base band resources compared to SF32 and thus it has direct impact on the amount of users that can be allocated.

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

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

Dimensioning WCDMA RAN: Flexi BTS Baseband Multi RAB

DN0981084 Issue 02D


DND 126 (128)))

7 Multi RAB

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

HSDPA + AMR call;

HSUPA + AMR call;

HSUPA/HSDPA + HSUPA/HSDPA call;

DCH + DCH call;

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.

7.1 HSDPA + AMR call resource allocation

If UE has active HSDPA service (UL: Rel.99, DL: HSDPA) while AMR on DCH service is established, resources for the AMR service are allocated on the same System Module where HSDPA resources are allocated.

For example:

- two System Modules FSME + FSMD,

- HSDPA scheduler(s) activated only at Master System Module (FSME)

- Extension System Module processes Rel99 traffic only

The resources for AMR service of Multi RAB call are allocated only at FSME where HSDPA service is allocated (Master System Module). DCH service of Multi RAB call consumes Rel99 CE licenses in UL/DL for DCH processing.

Multi RAB


127 (128)))



7.2 HSUPA + AMR call resource allocation

If 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 for processing, nor Rel99 CE licenses in UL/DL are required.

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

Set up of an AMR service with ongoing HSPA connection may have an impact on available baseband resources depending whether FDPCH feature is actively used by the UE:

- HSPA non-FDPCH connection: the newly established AMR service of Multi RAB call is not having any impact on available baseband resources;

- HSPA FDPCH connection: if AMR service of Multi RAB call is newly set up, the HSUPA connection is considered as HSUPA non-FDPCH from the baseband resource consumption point of view.

7.3 HSUPA/HSDPA + HSUPA/HSDPA call resource allocation

Each HSUPA/HSDPA service of a Multi RAB call requires UL/DL baseband resources for processing. One UE with Mutli RAB service counts as one UE from HSUPA and HSDPA Processing Set licenses allowed users point of view.

For example:

o one HSDPA Processing Set 1 (supports up to 32 HSDPA users),

o one HSUPA Processing Set (supports up to 24 HSUPA users),

o one UE with two RABs,

Still 23 HSUPA users can be served simultaneously with one Multi RAB UE considering HSUPA license (user count) point of view. Adequately in case of HSDPA Processing Sets, up to 31 HSDPA users can be served in addition to one Multi RAB UE.

HSDPA scheduler supports up to 238 HSDPA UEs in addition to one HSDPA Multi RAB UE with two RABs.

In addition to one HSUPA Multi RAB UE with two RABs, HSUPA scheduler supports up to:

238 HSUPA UEs (System Module Rel.2)

238 HSUPA UEs (System Module Rel.3 – Normal HSPA configuration)

158 HSUPA UEs (System Module Rel.3 – Small HSPA configuration)

Dimensioning WCDMA RAN: Flexi BTS Baseband Multi RAB

DN0981084 Issue 02D


DND 128 (128)))

7.4 DCH + DCH call resource allocation

Each DCH service of a Multi RAB call requires separate Rel99 CE baseband resources in UL/DL for processing. In case Multi RAB call, equivalent amount of R99CEs is consumed as in case of separate DCH Single RAB calls.

Rel99 CE licenses for each DCH service in Multi RAB call are required according to bearer rate. For example 64/64kbps + 64/128kbps Multi RAB baseband resource reservation is same as baseband resource reservation for 64/64kbps and 64/128kbps Single RABs.

wran dim flexi bts bb-0900d80580a2180a

Documents