Wram Dim Flexi Lite Bb-0900d80580a1ed72

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

Dimensioning WCDMA RAN: Flexi Lite BTS

DN709141912 Issue 01A

Approval date 2013-07-26

Disclaimer Dimensioning WCDMA RAN: Flexi Lite BTS

2 /52 Copyright © 2013 Nokia Solutions and Networks. All rights reserved.

DN70118388 Issue 061A

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.

Nokia Solutions and Networks are continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for additional information.

Table of Contents

This document has 51 pages.

Disclaimer 2

Table of Contents ................................................................................................................... 3

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

List of Figures and Tables ...................................................................................................... 6

1 Introduction ..................................................................................................... 8

2 Flexi Lite BTS .................................................................................................. 9

2.1 Flexi Lite BTS capacity .................................................................................. 10

2.1.1 Flexi Lite BTS system baseband capacity details .......................................... 10

2.2. Common Control Channels ........................................................................... 12

2.3. Dedicated Channels ...................................................................................... 14

2.3.1 Asymmetric UL/DL Rel99 CE allocation ........................................................ 15

3 HSDPA and BTS dimensioning ..................................................................... 16

3.1 HSDPA scheduler ......................................................................................... 16

3.2 Tcell grouping with Flexi Lite BTS ................................................................. 17

3.3 HSDPA BTS Processing Set ......................................................................... 17

3.4 Associated UL/DL DCH ................................................................................. 17

4 HSUPA and BTS dimensioning ..................................................................... 19

4.1 HSUPA resource steps ................................................................................. 19

4.2 HSUPA resource allocation ........................................................................... 20

4.3 HSUPA static allocation ................................................................................ 46

4.4 Interference Cancellation unit (PIC pool) ....................................................... 47

4.5 HS Cell_FACH users ..................................................................................... 47

4.6 CS Voice over HSPA users allocation ........................................................... 48

4.7 E-TFCI table selection ................................................................................... 49

4.8 HSUPA BTS Processing Set resources allocation ......................................... 49

5 Multi RAB ...................................................................................................... 51

5.1 HSDPA + AMR call resource allocation ......................................................... 51

5.2 HSUPA + AMR call resource allocation ......................................................... 51

Table of Contents Dimensioning WCDMA RAN: Flexi Lite BTS


DN70118388 Issue 061A

5.3 HSUPA/HSDPA + HSUPA/HSDPA call resource allocation .......................... 52

5.4 DCH + DCH call resource allocation .............................................................. 52

Configuring WCDMA RAN Transport, Rel. RU40 Summary of changes

DN70118388 Issue 06

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

5/52

Summary of changes

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

Changes made between issues 01 (2013-06-11, RU40) and 01A (2013-07-26, RU40)

Equation 1 Amount of allowed by hybrid HSUPA Processing Set HSUPA users has been updated.

Issue 01 (2013-06-11, RU40)

This is the first issue of this document.

List of Figures and Tables Dimensioning WCDMA RAN: Flexi Lite BTS


DN70118388 Issue 061A

List of Figures and Tables

Figure 1 Flexi Lite BTS (Baseband unit + RF unit + optional antenna + Ethernet ports)……………………………………………………………………………………...Error! Bookmark not defined.

Figure 2 Flexi Lite BTS subunits capacity…………………………………………..Error! Bookmark not defined.

Figure 3 Flexi Lite BTS LCG configuration types………………………………….Error! Bookmark not defined.

Figure 4 Example of Rel99 CE allocation…………………………………...........Error! Bookmark not defined.

Figure 5 HSUPA resource steps……………………………………………………Error! Bookmark not defined.

Figure 6 Exemplary license overlapping scenario………………………… ……..Error! Bookmark not defined.

Figure 7 Example scenario: hybrid HSUPA resource steps and Rel99 CE license overlapping……………………………………………………………………………..Error! Bookmark not defined.

Table 1 Flexi Lite BTS traffic capacity……………………………………… ……..Error! Bookmark not defined.

Table 2 Baseband resources required per one Rel99 traffic channel…………Error! Bookmark not defined.

Table 3 Flexi Lite BTS HSDPA scheduler details………………………………..Error! Bookmark not defined.

Table 4 Associated DCH and Rel99 CE usage…………………………………..Error! Bookmark not defined.

Table 5 HSUPA resource allocation in number of subunits (F-DPCH 10ms TTI users)……………………………………………………………………………………Error! Bookmark not defined.

Table 6 HSUPA resource allocation in number of subunits (non-F-DPCH 10ms TTI users) (tentative values)………………………………………………………….Error! Bookmark not defined.

Table 7 HSUPA resource allocation in number of subunits (F-DPCH 2ms TTI users) (tentative values)………………………………………………………………Error! Bookmark not defined.

Table 8 HSUPA resource allocation in number of subunits (non-F-DPCH 2ms TTI users) (tentative

Configuring WCDMA RAN Transport, Rel. RU40 List of Figures and Tables

DN70118388 Issue 06


7/52

values)………………………………………………………….Error! Bookmark not defined.

Table 9 HSUPA 16QAM transmitting UEs subunits requirement………………Error! Bookmark not defined.

Table 10 HSUPA static resources allocation……………………………………. Error! Bookmark not defined.

Table 11 HS-FACH users baseband requirements………………………………Error! Bookmark not defined.

Table 12 CS Voice over HSPA users………………………………………………Error! Bookmark not defined.

Introduction Dimensioning WCDMA RAN: Flexi Lite BTS


DN70118388 Issue 061A

1 Introduction

This dimensioning guideline is focused on Flexi Lite BTS dimensioning in RU40 covering WBTS8.0 release. Flexi Lite’s 1st release features the RU30 EP2 parity.

Configuring WCDMA RAN Transport, Rel. RU40 Flexi Lite BTS

DN70118388 Issue 06


9/52

2 Flexi Lite BTS

A BTS type called Flexi Lite BTS has been available in RU40 On Top. Flexi Lite BTS is a new, small-sized WCDMA BTS that can be used in various indoor and outdoor installation options (such as floor, wall, stand, pole, mast, lamp and other street furniture).

Flexi Lite BTS is extremely compact BTS that consists of baseband processing unit, RF module unit, integrated antenna (for optional use) and Ethernet ports included in one small box:

RF module unit provides the Radio Frequency (RF) functionality. RF module unit provides up to 10W + 10W output power supporting MIMO (up to two MIMO cells per BTS). Maximum of two carriers (two cells per carrier) can be configured with Flexi Lite BTS. With one sector (omni) configuration Flexi Lite BTS supports 2-way Rx Div while if two sectors are configured, then 1-way Rx Div is supported.

Baseband processing unit baseband processing as well as control and transmission functionality.

Optional integrated antenna with gain > 6dBi. If needed external antenna can be used.

Ethernet ports providing IP transport.

Figure 1 Flexi Lite BTS (Baseband unit + RF unit + optional antenna + Ethernet ports)

Flexi Lite BTS Dimensioning WCDMA RAN: Flexi Lite BTS


DN70118388 Issue 061A

2.1 Flexi Lite BTS capacity

Flexi Lite BTS provides up to 4 cell capacity with two sectors or up to 2 cells with single carrier. The output power option of max 10W + 10W per BTS is available.

Flexi Lite BTS consists of HW Rel.3 baseband unit providing capacity of 2,5 subunits.

Figure 2 Flexi Lite BTS subunits capacity

2.1.1 Flexi Lite BTS system baseband capacity details

The Flexi Lite BTS baseband unit consists of subunits that can be used for the following:

CCCH processing

R99 users processing

HSDPA users, and throughput processing

HSUPA users and throughput processing

CS Voice over HSPA users processing

Interference cancellation processing

Note that Flexi Lite BTS contains baseband resources for Common Control Channels processing for 4 cells/15 km cell range, 3 cells/20km cell range or 2 cells/30km configurations included in the BTS capacity. However, from practical side (indoor/outdoor micro cell environment) lower cell ranges are expected (for example, 100/300/500 meters).

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

The maximum available baseband capacity of Flexi Lite BTS for pure traffic depends on:

Local Cell Group (LCG) configuration type

Activated Interference Cancellation unit (PIC pool)

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

HS_Cell_FACH static resources (optional static reservation for HS-FACH UL users)


DN70118388 Issue 06


11/52

Local Cell Grouping functionality allows splitting available BTS baseband capacity into baseband pools responsible for processing traffic from dedicated group of cells. Local Cells Grouping functionality is frequently used for Flexi Multiradio BTS to create dedicated baseband resources for group of cells. Flexi Lite BTS supports in maximum four cells and therefore only one LCG can be created.

There are two LCG configuration types available for Flexi Lite BTS which describes BTS HSPA traffic processing capability, namely:

Rel.99 only configuration

Small HSPA configuration

The LCG configuration type is set during BTS commissioning using HSPA

setting parameter. If not commissioned, then Small HSPA configuration is

assumed by default.

Figure 3 Flexi Lite BTS LCG configuration types

Small HSPA configuration activates HSDPA scheduler and allocates 0,625 subunits for scheduler purpose.

Table 1 presents the Flexi Lite BTS capacity for traffic use for Rel.99 only and Small HSPA configuration (HSDPA scheduler activated)

LCG configuration type

Flexi Lite BTS traffic capacity

(subunits)



DN70118388 Issue 061A

LCG configuration type

Flexi Lite BTS traffic capacity

(subunits)

Rel.99 only 2.5

Small HSPA 1,875

Table 1 Flexi Lite BTS traffic capacity

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

In this document, it is assumed that Flexi Lite BTS cell range is not higher than 15km. For such cell range even with 4 cells, Flexi Lite BTS does not require any additional baseband resources for CCCH processing. However, if for some reasons, higher cell range is needed (for example, more than 15km with 4 cells or more than 30km with 2 cells) additional baseband resources and CCCH license key might be needed. For such situation, see RU40 Baseband Dimensioning: Flexi Multiradio BTS Guideline, CCCH dimensioning rules for Flexi System Module Rel.3 (FSMF) BTS.

2.2.1 Capacity licenses

The Flexi Multiradio WCDMA BTS and Flexi Lite 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 BTS exists in high volumes in the network, Nokia


DN70118388 Issue 06


13/52

Solutions and Networks does not generate licenses for these network elements directly (NE licenses), but a 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.

There are four types of capacity licenses, namely:

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

configurations or extended cell range case)

Rel99 CE license - Applicable for Rel99 traffic

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

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

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

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, consumes one HSDPA Processing Set 1 license capacity.

The HSUPA BTS processing set describes the maximum HSUPA that allows reaching a certain number of HSUPA users and UL throughput.

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 is able to fulfill the simultaneous x * 5.8Mbps and x * 24 users requirement. 1,75 subunits is the maximum that 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.

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



DN70118388 Issue 061A

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

License files available at BTS are limited with commissioned licenses. For example, if 100 R99CE license file is available at BTS, while commissioned

numberOfR99ChannelElements is set to 90, then BTS shall only use 90 R99

CE licenses.

2.3. 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 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 and 12 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/Backgrou

nd PS 16 64 128 1 1


nd PS 32 32 64 2 2


DN70118388 Issue 06


15/52


nd PS 64 16 32 4 4


nd PS 128 8 16 4 4


nd PS 256 4 8 6 6


nd PS 384 4 8 8 8

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 2 Baseband resources required per one Rel99 traffic channel

2.3.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 CE reservation is 4 CE in UL and 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 4 Example of Rel99 CE allocation

HSDPA and BTS dimensioning Dimensioning WCDMA RAN: Flexi Lite BTS


DN70118388 Issue 061A

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 document. For more specific information related to HSDPA, see HSDPA in BTS document.

3.1 HSDPA scheduler

There is one type of HSDPA scheduler available with Flexi Lite BTS which is activated when Small HSPA configuration has been commissioned. Note that when LCG configuration type has not been commissioned at all, then by default Small HSPA configuration is assumed.

The HSDPA scheduler supports 64QAM, MIMO, and DC-HSDPA features serving up to 180 HSDPA users from one to four cells. With DC-HSDPA feature and four cells, the maximum downlink HSDPA throughput is 84Mbps. After scheduler activation there is no need to allocate any additional baseband resources to reach 84Mbps.

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

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

throughput steps (HSDPA Throughput Step). Operator can select HSDPA

throughput step values from 1 up to 35. The HSDPA throughput step can be used to limit HSDPA scheduler throughput. Each HSDPA throughput step corresponds to 7.2Mbps.

For example:

Small HSPA configuration (1 HSDPA schedulers)

Commissioned HSDPA throughput step of HSDPA scheduler equal to 2

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

The table below presents the capability of single HSDPA scheduler.

Configuring WCDMA RAN Transport, Rel. RU40 HSDPA and BTS dimensioning

DN70118388 Issue 06


17/52

Max. number of active users per

HSDPA scheduler

Max. number of active users per

cell

Max number of cells assign to

HSDPA scheduler

Max scheduler

throughput

180 128 4 84 Mbps

Table 3 Flexi Lite BTS HSDPA scheduler details

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

3.2 Tcell grouping with Flexi Lite BTS

Tcell grouping is used to group cells to the HSDPA scheduler. Tcell groups 1 and 3 are handled by the Flexi Lite BTS scheduler.

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

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

Group 1: Tcell values 0, 1 and 2

Group 3: Tcell values 6, 7 and 8

3.3 HSDPA BTS Processing Set

HSDPA scheduler requires HSDPA license so called HSDPA BTS processing set providing user and throughput capacity. To learn more about HSDPA BTS processing sets, see chapter 2.2.1.

Since only one HSDPA scheduler can be activated, all licensed capacity is directly dedicated to the scheduler.

3.4 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 Error! Reference source not found. below.

HSDPA and BTS dimensioning Dimensioning WCDMA RAN: Flexi Lite BTS


DN70118388 Issue 061A

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

Configuring WCDMA RAN Transport, Rel. RU40 HSUPA and BTS dimensioning

DN70118388 Issue 06


19/52

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

The minimum HSUPA baseband allocation is 0 subunits. In this case, only HSUPA MAC-e is active. At least one HSUPA BTS processing set and HSDPA BTS processing set license is required (HSUPA user consumes one user capacity from both HSUPA BTS Processing Set and HSDPA BTS Processing Set license).

HSUPA is supported only with the co-existence of HSDPA. To activate HSPA, Small HSPA configuration needs to be commissioned. The HSUPA scheduler supports up to 140 HSUPA users from one to four cells.

4.1 HSUPA resource steps

HSUPA baseband resource allocation is done with specific sizes of resource steps. The amount of required resources depends on the desired throughput and the number of data HSUPA users. HSUPA scheduler allocates available baseband resources according to available HSUPA license and traffic conditions.

Baseband resources allocated for HSUPA purpose can change dynamically, based on current need (number of active users and combined L1 throughput of all data 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.125 subunit.

HSUPA and BTS dimensioning Dimensioning WCDMA RAN: Flexi Lite BTS


DN70118388 Issue 061A

Figure 5 HSUPA resource steps

HSUPA activation does not require fixed processing resources when the feature is being activated. At least one HSUPA BTS processing set and HSDPA BTS processing set license is required (note that HSUPA user consumes one user capacity from both HSUPA BTS Processing Set and HSDPA BTS Processing Set license).

4.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 scheduler, depends on the amount of available HSUPA BTS processing sets.

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

To allocate the next HSUPA resource step, an additional free capacity of 6 Rel99 CE is needed. The required 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 to be back immediately after its allocation.

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


DN70118388 Issue 06


21/52

Figure 6 Exemplary license overlapping scenario

One HSUPA BTS Processing Set per BTS (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 1 Amount of allowed by hybrid HSUPA Processing Set HSUPA users

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



DN70118388 Issue 061A

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, the HSUPA throughput might also 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. Each 6 Rel99 CE decrease amount of hybrid HSUPA resource steps available for HSUPA scheduler according to formula below:

Amount_of_hybrid_HSUPA_resource_steps_for_HSUPA_purpose =

8 – Roundup(Amount_of_allocated_Rel99_CE / 6)

Where:

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:

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.


DN70118388 Issue 06


23/52

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

Amount_of_hybrid_HSUPA_resource_steps_for_HSUPA_purpose =

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

Figure 7 Example scenario: hybrid HSUPA resource steps and REl99 CE license overlapping

For overlapping R99 CE licenses and licensed HSUPA resources, commissioning can be performed 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



DN70118388 Issue 061A

HSUPA resource steps can be statically commissioned for HSUPA (see chapter 4.3). Note that hybrid HSUPA Processing Set is always dynamic and cannot be statically reserved.


DN70118388 Issue 06


25/52

HSUPA data UEs

per HSUPA scheduler

Baseband minimum decoding capacity [Mbps]

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

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

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

Table 5 HSUPA resource allocation in number of subunits (F-DPCH 10ms TTI users)



DN70118388 Issue 061A

Table 5 HSUPA resource allocation in number of subunits (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

41~44 0,62

5 0,625 0,75 0,875 1 1,12

5 1,25 1,375 1,5 1,625 1,75 1,75 N/A N/A N/A N/A N/A N/A

45~48 0,62

5 0,625 0,75 0,875 1 1,25 1,375 1,5 1,5 1,625 N/A N/A N/A N/A N/A N/A N/A N/A



57~60 0,75 0,75 0,75 1 1,125 1,37

5 1,5 1,625 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A

61~64 0,87

5 0,875 0,875 1 1,25 1,37

5 1,5 1,625 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A

65~68 0,87

5 0,875 0,875 1,125 1,25 1,37

5 1,625 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

69~72 1 1 1 1,125 1,25 1,5 1,625 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

73~76 1 1 1 1,125 1,25 1,5 1,625 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

77~80 1 1 1 1,125 1,375 1,5 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

81~100 1,25 1,25 1,25 1,25 1,5 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

101~120 1,5 1,5 1,5 1,5 1,625 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

121~140 1,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 N/A


DN70118388 Issue 06


27/52

Table 5 HSUPA resource allocation in number of subunits (F-DPCH 10ms TTI users) - cont.

HSUPA data UEs per HSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9

1 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







17~18 1,25 1,25 N/A N/A N/A N/A

19~20 1,25 1,25 1,5 1,5 N/A N/A

21~22 1,25 1,25 1,5 1,5 1,75 1,75

23~24 1,25 1,25 1,5 1,5 1,75 1,75

25~26 1,25 1,25 1,5 1,5 1,75 1,75

27~28 1,25 1,25 1,5 1,5 1,75 1,75

29~30 1,5 1,75 1,75 1,75 1,75 1,75

31~32 1,5 1,75 1,75 1,75 1,75 1,75

33~34 1,5 1,75 1,75 1,75 1,75 1,75






DN70118388 Issue 061A

Table 5 HSUPA resource allocation in number of subunits (F-DPCH 10ms TTI users) - cont.

HSUPA data UEs

per HSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9












101~120 N/A N/A N/A N/A N/A N/A

121~140 N/A N/A N/A N/A N/A N/A


DN70118388 Issue 06


29/52

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


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

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

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

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

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

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

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

39~40 1 1 1 1 1,125 1,25 1,375 1,5 1,625 1,75 1,75 N/A N/A N/A N/A N/A N/A N/A

Table 6 HSUPA resource allocation in number of subunits (non F-DPCH 10ms TTI users) (tentative values)



DN70118388 Issue 061A

Table 6 HSUPA resource allocation in number of subunits (non-F-DPCH 10ms TTI users) (tentative values) – 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


45~48 1,25 1,25 1,25 1,25 1,25 1,375 1,5 1,625 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A

49~52 1,375 1,375 1,375 1,375 1,375 1,375 1,5 1,625 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A





69~72 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







DN70118388 Issue 06


31/52

Table 6 HSUPA resource allocation in number of subunits (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








13~14 1,62

5 1,75 1,75 N/A N/A N/A

15~16 1,75 N/A N/A N/A N/A N/A

17~18 1,75 N/A N/A N/A N/A N/A

19~20 1,75 N/A N/A N/A N/A N/A












DN70118388 Issue 061A

HSUPA data UEs

per HSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9



DN70118388 Issue 06


33/52


HSUPA data UEs

per HSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9












101~120 N/A N/A N/A N/A N/A N/A

121~140 N/A N/A N/A N/A N/A N/A



DN70118388 Issue 061A

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

1 0,12

5 0,12

5 0,37

5 0,37

5 0,37

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

2 0,12

5 0,12

5 0,37

5 0,37

5 0,37

5 0,37

5 0,62

5 0,62

5 0,62

5 N/A N/A N/A N/A N/A N/A N/A N/A

3~4 0,12

5 0,25 0,5 0,5 0,62

5 0,75 0,75 0,75 0,75 0,75 0,75 0,87

5 1 1,37

5 1,37

5 1,37

5 1,375

5~6 0,12

5 0,25 0,5 0,5 0,62

5 0,75 0,87

5 1 1 1 1 1 1 1,37

5 1,37

5 1,37

5 1,375

7~8 0,12

5 0,25 0,5 0,5 0,62

5 0,87

5 0,87

5 1 1,25 1,37

5 1,37

5 1,37

5 1,37

5 1,37

5 1,37

5 1,37

5 1,375

9~10 0,12

5 0,25 0,5 0,5 0,62

5 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,62

5 1,62

5 1,62

5 1,62

5 1,625

11~12 0,25 0,25 0,5 0,5 0,62

5 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

13~14 0,25 0,25 0,5 0,62

5 0,62

5 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

15~16 0,25 0,37

5 0,5 0,62

5 0,62

5 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

17~18 0,25 0,37

5 0,5 0,75 0,75 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

19~20 0,25 0,37

5 0,5 0,75 0,75 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

21~22 0,37

5 0,37

5 0,5 0,75 0,87

5 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

23~24 0,37 0,37 0,5 0,75 1 1 1 1 1,25 1,37 1,37 1,62 1,75 1,75 N/A N/A N/A


DN70118388 Issue 06


35/52

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

5 5 5 5 5

25~26 0,37

5 0,37

5 0,5 0,75 1 1 1 1 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

27~28 0,37

5 0,37

5 0,62

5 0,75 1 1,12

5 1,25 1,25 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

29~30 0,37

5 0,37

5 0,62

5 0,75 1 1,12

5 1,25 1,25 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

31~32 0,5 0,5 0,62

5 0,75 1 1,12

5 1,25 1,25 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

33~34 0,5 0,5 0,62

5 0,75 1 1,12

5 1,37

5 1,37

5 1,37

5 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

35~36 0,5 0,5 0,62

5 0,75 1 1,25 1,37

5 1,5 1,5 1,5 1,5 1,62

5 1,75 1,75 N/A N/A N/A

37~38 0,5 0,5 0,62

5 0,87

5 1 1,25 1,37

5 1,5 1,5 1,5 1,5 1,62

5 1,75 1,75 N/A N/A N/A

39~40 0,5 0,5 0,75 0,87

5 1 1,25 1,37

5 1,62

5 1,62

5 1,62

5 1,62

5 1,62

5 1,75 1,75 N/A N/A N/A

Table 7 HSUPA resource allocation in number of subunits ( F-DPCH 2ms TTI users) (tentative values)



DN70118388 Issue 061A

Table 7 HSUPA resource allocation in number of subunits (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

41~44 0,62

5 0,62

5 0,75 0,87

5 1 1,25 1,37

5 1,62

5 1,75 1,75 1,75 1,75 1,75 1,75 N/A N/A N/A

45~48 0,62

5 0,62

5 0,75 0,87

5 1 1,25 1,37

5 1,62

5 N/A N/A N/A N/A N/A N/A N/A N/A N/A

49~52 0,75 0,75 0,87

5 1 1 1,25 1,5 1,62


53~56 0,75 0,75 0,87

5 1 1,12

5 1,25 1,5 1,62


57~60 0,75 0,75 0,87

5 1 1,12

5 1,25 1,5 1,62


61~64 0,87

5 0,87

5 0,87

5 1,12

5 1,12

5 1,37

5 1,5 1,62


65~68 0,87

5 0,87

5 0,87

5 1,12

5 1,25 1,37

5 1,5 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A

69~72 1 1 1 1,12

5 1,25 1,37


73~76 1 1 1 1,25 1,25 1,37


77~80 1 1 1 1,25 1,37

5 1,5 1,62

5 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A

81~100 1,25 1,25 1,25 1,25 1,62

5 1,62

5 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

101~120 1,5 1,5 1,5 1,5 1,62


121~140 1,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


DN70118388 Issue 06


37/52


HSUPA data UEs

per HSUPA scheduler


24.6 26.1 27.5 29 30.4 31.9




5~6 1,625 1,625 1,625 1,75 N/A N/A

7~8 1,625 1,625 1,625 1,75 N/A N/A

9~10 1,625 1,625 1,625 1,75 N/A N/A


















DN70118388 Issue 061A


HSUPA data UEs per HSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9












101~120 N/A N/A N/A N/A N/A N/A

121~140 N/A N/A N/A N/A N/A N/A


DN70118388 Issue 06


39/52

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

1 0,12

5 0,12

5 0,37

5 0,37

5 0,37


2 0,12

5 0,12

5 0,37

5 0,37

5 0,37

5 0,37

5 0,62

5 0,62

5 0,62

5 N/A N/A N/A N/A N/A N/A N/A N/A

3~4 0,12

5 0,25 0,5 0,5 0,62

5 0,75 0,75 0,75 0,75 0,75 0,75 0,87

5 1 1,37

5 1,37

5 1,375 1,375

5~6 0,12

5 0,25 0,5 0,5 0,62

5 0,75 0,87

5 1 1 1 1 1 1 1,37

5 1,37

5 1,375 1,375

7~8 0,12

5 0,25 0,5 0,5 0,62

5 0,87

5 0,87

5 1 1,25 1,37

5 1,37

5 1,37

5 1,37

5 1,37

5 1,37

5 1,375 1,375

9~10 0,12

5 0,25 0,5 0,5 0,62

5 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,62

5 1,62

5 1,62

5 1,625 1,625

11~12 0,25 0,25 0,5 0,5 0,62

5 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

13~14 0,25 0,25 0,5 0,62

5 0,62

5 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

15~16 0,25 0,37

5 0,5 0,62

5 0,62

5 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

17~18 0,25 0,37

5 0,5 0,75 0,75 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

19~20 0,25 0,37

5 0,5 0,75 0,75 0,87

5 1 1 1,25 1,37

5 1,37

5 1,62

5 1,75 1,75 N/A N/A N/A

21~22 0,62

5 0,62

5 0,75 0,87

5 1 1 1 1,12

5 1,25 1,37

5 1,5 1,62

5 1,75 N/A N/A N/A N/A



DN70118388 Issue 061A

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

23~24 0,62

5 0,62

5 0,75 0,87

5 1 1,12

5 1,12

5 1,12

5 1,25 1,37

5 1,5 1,62

5 1,75 N/A N/A N/A N/A

25~26 0,75 0,75 0,75 1 1 1,12

5 1,12

5 1,12

5 1,25 1,37

5 1,5 1,62

5 1,75 N/A N/A N/A N/A

27~28 0,75 0,75 0,87

5 1 1,12

5 1,25 1,25 1,25 1,25 1,37

5 1,5 1,62

5 1,75 N/A N/A N/A N/A

29~30 0,75 0,75 0,87

5 1 1,12

5 1,25 1,37

5 1,37

5 1,37

5 1,37

5 1,5 1,62

5 1,75 N/A N/A N/A N/A

31~32 0,87

5 0,87

5 0,87

5 1 1,12

5 1,25 1,37

5 1,37

5 1,37

5 1,37

5 1,5 1,62

5 1,75 N/A N/A N/A N/A

33~34 0,87

5 0,87

5 1 1,12

5 1,25 1,37

5 1,5 1,5 1,5 1,5 1,5 1,62

5 1,75 N/A N/A N/A N/A

35~36 0,87

5 0,87

5 1 1,12

5 1,25 1,37

5 1,5 1,62

5 1,62

5 1,62

5 1,62

5 1,62

5 1,75 N/A N/A N/A N/A

37~38 1 1 1 1,12

5 1,25 1,37

5 1,5 1,62

5 1,62

5 1,62

5 1,62

5 1,62

5 1,75 N/A N/A N/A N/A

39~40 1 1 1,12

5 1,25 1,37

5 1,5 1,62

5 1,75 1,75 1,75 1,75 1,75 1,75 N/A N/A N/A N/A

Table 8 HSUPA resource allocation in number of subunits (non F-DPCH 2ms TTI users) (tentative values)


DN70118388 Issue 06


41/52


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

41~44 1,12

5 1,12

5 1,12

5 1,25 1,37

5 1,5 1,62

5 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A

45~48 1,25 1,25 1,25 1,37

5 1,5 1,62


49~52 1,37

5 1,37

5 1,37

5 1,37

5 1,5 1,62


53~56 1,5 1,5 1,5 1,5 1,62

5 1,75 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

57~60 1,5 1,5 1,5 1,62

5 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

61~64 1,62

5 1,62

5 1,62

5 1,62

5 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

65~68 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 N/A

69~72 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








DN70118388 Issue 061A


HSUPA data UEs

per HSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9




5~6 1,625 1,625 1,625 1,75 N/A N/A

7~8 1,625 1,625 1,625 1,75 N/A N/A

9~10 1,625 1,625 1,625 1,75 N/A N/A

















DN70118388 Issue 06


43/52


HSUPA data UEs

per HSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9 33.3

41~44 N/A N/A N/A N/A N/A N/A N/A















DN70118388 Issue 061A

In Table 5-8 the assumption is - the HSUPA licensed capacity is limited, as well as the typical use case when the majority of the users are DL data dominated and the remaining users are UL data dominated.

In Table 5-8 the assumption is - 16QAM is not used.

When HSUPA 16QAM is in use, three UEs transmitting with 16QAM modulation requires one subunit form Flexi Lite BTS.

Number of HSUPA 16QAM transmitting UEs

Required amount of subunits

1 0,375

2 0,625

3 0,875

Table 9 HSUPA 16QAM transmitting UEs subunits requirement

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.5 Mbps (16QAM). Only one 16QAM transmitting user can be located in the given subunit (TTI) per cell.

HSUPA scheduler can allocate 1.75 subunits in the maximum.

To calculate the subunits reservation for mixed user type case, (F-DPCH/no-FDPCH/2ms TTI/10msTTI users, 16QAM transmitting users 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 2 HSUPA subunits formula

where:


DN70118388 Issue 06


45/52

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

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

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

No-F-DPCH_10msTTI_Subunits – subunits required for HSUPA no-F-DPCH 10ms TTI users, calculated from 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:

HSUPA BTS combined L1 throughput = 17.3Mbps;

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

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

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

Number of no-F-DPCH 10ms TTI users = 15 UEs with 4.3Mbps throughput;

F-DPCH_2msTTI_Subunits – 0.625 subunits required; see Error! Reference source not found. (8 users, 5.8Mbps combined L1 thr);

F-DPCH_10msTTI_Subunits – 0.5 subunits required; see Error! Reference source not found. (10 users, 2.9Mbps combined L1 thr);

No-F-DPCH_2msTTI_Subunits – 0.5 subunit required; see Error! Reference source not found. (9 users, 4.3Mbps combined L1 thr);

No-F-DPCH_10msTTI_Subunits – 0.75 subunits required; see Error! Reference source not found. (15 users, 4.3Mbps combined L1 thr);



DN70118388 Issue 061A

According to

Equation 2: HSUPA_subunits = 0.625 + 0.5 + 0.5 + 0.75 = 2,375

Therefore: 2,375 subunits for HSUPA users are required.

4.3 HSUPA static allocation

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

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


DN70118388 Issue 06


47/52

23-24 0.625 0.625 0.75 1 1

Table 10 HSUPA static resources allocation

HSUPA throughput may be bigger if there is more capacity available in the BTS.

4.4 Interference Cancellation unit (PIC pool)

To achieve high HSUPA throughput, the interference cancellation feature is recommended. Interference cancellation is performed with PIC pool unit. With the commissioning parameter, the operator can activate one PIC pool unit providing interference cancellation up to 4 cells at the same time.

PIC pool unit consumes capacity of one subunit.

4.5 HS Cell_FACH users

HS-FACH feature allows sending and receiving small packets of data Cell_FACH state using transmission on HSUPA and HSDPA channels (UL/DL). UE in Cell_FACH state does not require any capacity license.

HS-Cell_FACH user is treated as normal HSPA user with respect to maximum number of users supported by HSDPA and HSUPA schedulers.

HSUPA scheduler baseband resources are allocated in the same manner as for HSUPA data users. 10ms TTI HSUPA dimensioning tables ( ) should be used to determine HSUPA subunits consumption for HS Cell_FACH users.

However, if operator wants to guarantee certain amount of baseband resources for HS Cell_FACH user’s only, additional baseband resource might

be statically allocated. 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). Single step provides baseband capacity for 10 HS-FACH users (in maximum 40 HS-FACH users can be served in Flexi Lite BTS)

HS_FACH Flexi Lite BTS

HS-FACH users step baseband capacity

0.125 subunit



DN70118388 Issue 061A

reservation

Table 11 HS-FACH users baseband requirements

4.6 CS Voice over HSPA users allocation

CS Voice over HSPA users consumes subunits capacity. Up to 80 CS Voice over HSPA users can be allocated in one subunit.

Number of CS Voice over HSPA users Flexi Lite BTS

10 0.125

20 0.25

30 0.375

40 0.5

50 0.625

60 0.75

70 0.875

80 1 Table 12 CS Voice over HSPA users

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.


DN70118388 Issue 06


49/52

4.7 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 of 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, fewer 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. 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). See WCDMA RAN and I-HSPA RRM HSUPA document for E-TFCI table configuration details.

4.8 HSUPA BTS Processing Set resources allocation

Each HSUPA BTS processing set license increases the 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.



DN70118388 Issue 061A

In WN8.0, the HSUPA BTS Processing Set allows reaching 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 3 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.

For example:

Required amount of HSUPA users per BTS: 70 users

Required HSUPA L1 throughput per BTS: 11Mbps

Number_of_HSUPA_BTS_Processing_Sets = max {

Roundup (HSUPA_users / 24); Roundup (HSUPA_data_users_throughput / 5.8) } = max { Roundup( 70 / 24); Roundup (11 / 5.8 ) } = max { Roundup (2.91) ; Roundup(1.89) } = max { 3 ; 2} = 3

Three HSUPA BTS Processing Set licenses are required to fulfill scenario assumptions.

Configuring WCDMA RAN Transport, Rel. RU40 Multi RAB

DN70118388 Issue 06


51/52

5 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 BTS RRM HSDPA and WCDMA RAN BTS RRM HSUPA documents.

5.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 needs to be allocated.

5.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, neither Rel99 CE licenses in UL/DL are required.

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:

Multi RAB Dimensioning WCDMA RAN: Flexi Lite BTS


DN70118388 Issue 061A

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.

5.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:

one HSDPA Processing Set 1 (supports up to 32 HSDPA users),

one HSUPA Processing Set (supports up to 24 HSUPA users),

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.

5.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 of 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 the same with baseband resource reservation for 64/64kbps and 64/128kbps Single RABs.

Documents

Wram Dim Flexi Lite Bb-0900d80580a1ed72