ru40 flexi lite bts baseband dimensioning guidelive

8/10/2019 RU40 Flexi Lite BTS Baseband Dimensioning Guidelive

http://slidepdf.com/reader/full/ru40-flexi-lite-bts-baseband-dimensioning-guidelive 1/45

1 (45)) © Nokia Siemens Networks Confidential

WCDMA RAN, Rel.RU40, OperatingDocumentation

Dimensioning WCDMARAN: Flexi Lite BTS

INTERNAL GUIDELINE

Issue 01Approval Date: 2013-06-06

Please always check the latest version of this document under the following link:

https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/480036955

Confidential



Dimensioning WCDMA RAN: Flexi Lite BTS

DN09141912Issue 01

© Nokia Siemens Networks Confidential

2 (2 (45)))

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

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

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

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

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

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

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

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

Copyright © Nokia Siemens Networks 2013. All rights reserved.





Table of contents

Summary of changes ............................................................................... 4

List of Figures and Tables ....................................................................... 5

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

2 Flexi Lite BTS ....................................................................... 7

2.1 Flexi Lite BTS capacity........................................................... 8

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

2.2. Common Control Channels .................................................. 10

2.3. Dedicated Channels ............................................................. 11

2.3.1

Asymmetric UL/DL Rel99 CE allocation .............................. 12

3 HSDPA and BTS dimensioning ........................................ 14

3.1 HSDPA scheduler ................................................................ 14

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

3.3 HSDPA BTS Processing Set................................................ 15

3.4 Associated UL/DL DCH ........................................................ 15

4 HSUPA and BTS dimensioning ........................................ 17

4.1 HSUPA resource steps ........................................................ 17

4.2

HSUPA resource allocation.................................................. 18 4.3 HSUPA static allocation ....................................................... 39

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

4.5 HS Cell_FACH users ........................................................... 41

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

4.7 E-TFCI table selection.......................................................... 42

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

5 Multi RAB ............................................................................ 44

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

5.2

HSUPA + AMR call resource allocation ............................... 44 5.3 HSUPA/HSDPA + HSUPA/HSDPA call resource allocation 44

5.4 DCH + DCH call resource allocation .................................... 45



Dimensioning WCDMA RAN: Flexi BTS Baseband

DN09141912Issue 01


4 (4 (45)))

Summary of changes

The document comprises 45 pages.

This is the first issue of this document.





List of Figures and Tables

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

Figure 2 Flexi Lite BTS subunits capacity .............................................................................................. 8

Figure 3 Flexi Lite BTS LCG configuration types .................................................................................. 9

Figure 4 Example of Rel99 CE allocation .............................................................................................. 13

Figure 5 HSUPA resource steps ............................................................................................................ 18

Figure 6 Exemplary license overlapping scenario ............................................................................... 19

Figure 7 Example scenario: hybrid HSUPA resource steps and Rel99 CE license overlapping ..... 21

Table 1 Flexi Lite BTS traffic capacity ..................................................................................................... 9

Table 2 Baseband resources required per one Rel99 traffic channel ................................................ 12

Table 3 Flexi Lite BTS HSDPA scheduler details ................................................................................. 15

Table 4 Associated DCH and Rel99 CE usage ..................................................................................... 16

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

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

Table 7 HSUPA resource allocation in number of subunits (F-DPCH 2ms TTI users) (tentativevalues) ........................................................................................................................................ 30

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

Table 9 HSUPA 16QAM transmitting UEs subunits requirement ....................................................... 38

Table 10 HSUPA static resources allocation ........................................................................................ 40

Table 11 HS-FACH users baseband requirements ................................................................................ 41

Table 12 CS Voice over HSPA users ..................................................................................................... 42




DN09141912Issue 01


6 (6 (45)))

1 Introduction

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





2 Flexi Lite BTS

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

Flexi Lite BTS is extremely compact BTS that consists of baseband processing

unit, RF module unit, integrated antenna (for optional use) and Ethernet portsincluded in one small box:

RF module unit provides the Radio Frequency (RF) functionality. RFmodule unit provides up to 10W + 10W output power supporting MIMO (upto two MIMO cells per BTS). Maximum of two carriers (two cells per carrier)can be configured with Flexi Lite BTS. With one sector (omni) configurationFlexi 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 andtransmission functionality.

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

Ethernet ports providing IP transport.

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




DN09141912Issue 01


8 (8 (45)))

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

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 Channelsprocessing for 4 cells/15 km cell range, 3 cells/20km cell range or 2 cells/30kmconfigurations included in BTS capacity. However from practical side (indoor/outdoormicro cell environment) lower cell ranges are expected (for example: 100/300/500meters).

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

Local Cell Grouping functionality allows splitting available BTS baseband capacity intobaseband pools responsible for processing traffic from dedicated group of cells. LocalCells Grouping functionality is frequently used for Flexi Multiradio BTS to create





dedicated baseband resources for group of cells. Flexi Lite BTS supports in maximumfour cells and therefore only one LCG can be created.

There are two LCG configuration types available for Flexi Lite BTS which describes BTSHSPA traffic processing capability. The two LCG configuration types are as follow:

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

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

LCG configurationtype

Flexi Lite BTS traffic

capacity

(subunits)

Rel.99 only 2.5

Small HSPA 1,875

Table 1 Flexi Lite BTS traffic capacity




DN09141912Issue 01


10 (10 (45)))

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. Forsuch cell range even with 4 cells, Flexi Lite BTS does not require any additionalbaseband resources for CCCH processing. However, if from some reasons higher cellrange is needed (for example, more than 15km with 4 cells or more than 30km with 2cells) additional baseband resources and CCCH license key might be needed. For suchsituation, see RU40 Baseband Dimensioning: Flexi Multiradio BTS Guideline, CCCHdimensioning 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 thecapacity that the operator has purchased. The licensed capacity can be less than themaximum hardware capacity.

Flexi WCDMA BTS Baseband capacities are allocated according to the capacity licensefile. Because the BTS exists in high volumes in the network, Nokia Siemens Networksdoes 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 adedicated amount of features or capacity (pool license) and it is up to the user todetermine how these NE licenses are distributed towards the network elements.

There are four types of capacity licenses, namely:

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

configurations or extended cell range case)- Rel99 CE license

o Applicable for Rel99 traffic- HSDPA BTS Processing Set license

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

o Applicable for HSUPA throughput and HSDPA users





Rel99 CE license defines the maximum capacity for pure Rel99 traffic. HSDPA/HSUPAschedulers 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 formaximum user amount and throughput. Separate ASW (application software) licensesfor 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 HSDPAProcessing Set license point of view. For example, 32 Multi RAB UEs, each having twoHSDPA RABs, consume one HSDPA Processing Set 1 license capacity.

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

HSUPA BTS processing set provides simultaneously throughput (5.8Mbps) and useramount (24 HSUPA data/CS voice over HSPA users).

With x number of available HSUPA licenses, the HSUPA baseband reservation is able tofulfill the simultaneous x * 5.8Mbps and x * 24 users requirement. 1,75 subunits is themaximum 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 twoHSUPA RABs, consume one HSUPA Processing Set license.

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

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

NOTE:

License files available at BTS are limited with commissioned licenses. Forexample, 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 activeDCH user is required. Baseband resources are required per each DCH active user in “nohandover” state and per each DCH user in “soft handover” state. Additional basebandresources are not required either for users in softer handover state or compressed mode.




DN09141912Issue 01


12 (12 (45)))

For multi RAB cases, Rel99 CE requirements need to be calculated as a sum of Rel99CE 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

present required number of Rel99 CE per each active connection for basic set of RABs.

RAB Traffic classCS

/PS

Max Ratesfor each

RAB, kbps

Min SFRequired

Rel99 CE perconnection

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 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 raterequirements. The rule for allocating Submodule resources for asymmetric bit rates isbased 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 CEreservation 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 DLresources do not have to be allocated symmetrically across submodule/subunit UL andDL capacity (see Figure 12).

Figure 4 Example of Rel99 CE allocation




DN09141912Issue 01


14 (14 (45)))

3 HSDPA and BTS dimensioningSome supported capacities mentioned in this document may require separate licenses inthe RAN before they can be activated. For more information, see Licenses Managementin 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 activatedwhen Small HSPA configuration has been commissioned. Note that when LCGconfiguration type has not been commissioned at all, then by default Small HSPAconfiguration is assumed.

The HSDPA scheduler supports 64QAM, MIMO, and DC-HSDPA features serving up to180 HSDPA users from one to four cells. With DC-HSDPA feature and four cells, themaximum downlink HSDPA throughput is 84Mbps. After scheduler activation there is noneed 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 throughputcommissioning by the operator.

The operator can specify the maximum throughput for HSDPA scheduler. The maximumthroughput 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 schedulerthroughput. 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.





Max. number ofactive users per

HSDPAscheduler

Max. numberof activeusers per

cell

Max number ofcells assign to

HSDPAscheduler

Maxscheduler

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 numberof 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 arehandled by the Flexi Lite BTS scheduler.

The same Tcell values can be used by different cells if those are allocated to differentfrequency layers. With Dual Cell (DC) HSDPA feature cells from one sector should havethe 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 setproviding user and throughput capacity. To learn more about HSDPA BTS processingsets, see chapter 2.2.1.

Since only one HSDPA scheduler can be activated all licensed capacity is directlydedicated 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 asa normal DCH. See table below.




DN09141912Issue 01


16 (16 (45)))

User dataRel99 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;





4 HSUPA and BTS dimensioningSome supported capacities mentioned in this document may require separate licenses inthe RAN before they can be activated. For more information, see Licenses Managementin WCDMA RAN document. For more specific information related to HSUPA, see HSUPAin BTS document

Baseband capacity is reserved for HSUPA on a need basis. The baseband capacityallocation may be changed dynamically between DCH and HSUPA use. In the basebandallocation, DCH has a higher priority than HSUPA. The operator may commission aminimum fixed reservation for HSUPA, but the rest of the capacity is dynamicallyallocated to HSUPA when DCH does not need it.

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

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

4.1 HSUPA resource steps

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

Baseband resources allocated for HSUPA purpose can change dynamically, based oncurrent need (number of active users and combined L1 throughput of all data HSUPAusers). HSUPA baseband resource allocation is performed on a step basis. One HSUPAbaseband resource is called a HSUPA resource step. One HSUPA resource step

consumes 0.125 subunit.




DN09141912Issue 01


18 (18 (45)))

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 setlicense is required (note that HSUPA user consumes one user capacity from bothHSUPA 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 maximumbaseband resources that can be allocated for HSUPA scheduler, depends on amount ofavailable 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) exceed BTScapacity for traffic use, the overlapping baseband capacity can be dynamicallyexchanged between R99 and HSUPA users.

To allocate the next HSUPA resource step, an additional free capacity of 6 Rel99 CE isneeded. 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 thatthe 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 freeresources used by HSUPA.





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 havebeen consumed. Each utilized Rel99 CE, decreases amount of HSUPA users allowed byhybrid 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 usersfrom 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 usersconsumes Rel99 CE capacity (5 Rel99 CE) from hybrid HSUPA Processing Setlicense

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




DN09141912Issue 01


20 (20 (45)))

When R99 users consume hybrid HSUPA license capacity also HSUPA throughput mightbe 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 forHSUPA 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 ofhybrid HSUPA resource steps available for HSUPA scheduler allocation.

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

When baseband capacity is covered by hybrid HSUPA Processing Set license and Rel99CE licenses (license overlapping), formulas above take into consideration only notoverlapped Rel99 CE (allocated Rel.99 CE available with hybrid HSUPA Processing Setlicense 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) + 48Rel.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 areconsumed (108 Rel99 CE licenses + 8 Rel99 CE from hybrid HSUPA ProcessingSet license)

Amount_of_allowed_HSUPA_users_by_hybrid_HSUPA_Processing_Set = 24 – Roundup (Amount_of_allocated_Rel99_CE / 2) = 24 – Roundup (8 / 2) =24 – Roundup (4) = 24 – 4 = 20

Amount_of_hybrid_HSUPA_resource_steps_for_HSUPA_purpose =

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

After allocation of 8 Rel99 CE, hybrid HSUPA Processing Set license hascapacity of 20 HSUPA users and 6 HSUPA resource steps.





Figure 7 Example scenario: hybrid HSUPA resource steps and Rel99 CE licenseoverlapping

For overlapping R99 CE licenses and licensed HSUPA resources, commissioning can beperformed 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 (see chapter 4.3). Note that hybrid HSUPA Processing Set is alwaysdynamic and cannot be statically reserved.




DN09141912Issue 01


22 (22 (45)))

HSUPAdata UEs

per HSUPAscheduler

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)





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

HSUPAdata UEs

perHSUPA

scheduler


<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 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 N/A N/A N/A N/A N/A N/A

45~48 0,625 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,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

61~64 0,875 0,875 0,875 1 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


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




DN09141912Issue 01


24 (24 (45)))

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

HSUPA dataUEs perHSUPA

scheduler

Baseband minimum decoding capacity[Mbps]

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








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

HSUPAdata UEs

perHSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9


45~48 N/A N/A N/A N/A N/A N/A49~52 N/A N/A N/A N/A N/A N/A









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




DN09141912Issue 01


26 (26 (45)))

HSUPAdata UEs

per HSUPAscheduler


<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/A5~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 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)

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





HSUPAdata UEs

perHSUPA

scheduler


<1.0 1.0 2.0 2.9 4.3 5.8 7.2 8.7 10.1 11.6 13 14.5 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/A53~56 1,5 1,5 1,5 1,5 1,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 N/A


61~64 1,625 1,625 1,625 1,625 1,625 1,625 1,75 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 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

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









DN09141912Issue 01


28 (28 (45)))

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

HSUPAdata UEs

perHSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9


2 N/A N/A N/A N/A N/A N/A3~4 N/A N/A N/A N/A N/A N/A





13~14 1,625 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















HSUPAdata UEs

perHSUPA

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




DN09141912Issue 01


30 (30 (45)))

HSUPAdata UEs

per HSUPAscheduler


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

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

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

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

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,3757~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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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





HSUPAdata UEs

per HSUPAscheduler


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

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

45~48 0,625 0,625 0,75 0,875 1 1,25 1,375 1,625 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,875 1 1 1,25 1,5 1,625 N/A N/A N/A N/A N/A N/A N/A N/A N/A

53~56 0,75 0,75 0,875 1 1,125 1,25 1,5 1,625 N/A N/A N/A N/A N/A N/A N/A N/A N/A

57~60 0,75 0,75 0,875 1 1,125 1,25 1,5 1,625 N/A N/A N/A N/A N/A N/A N/A N/A N/A

61~64 0,875 0,875 0,875 1,125 1,125 1,375 1,5 1,625 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,375 1,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,625 1,625 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,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





DN09141912Issue 01


32 (32 (45)))


HSUPAdata UEs

per HSUPAscheduler


24.6 26.1 27.5 29 30.4 31.9



3~4 N/A N/A N/A N/A N/A N/A5~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





















HSUPA dataUEs perHSUPA

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




DN09141912Issue 01


34 (34 (45)))

HSUPAdata UEs

per HSUPAscheduler


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

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

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

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,3755~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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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






HSUPAdata UEs

per HSUPAscheduler


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


45~48 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 N/A

49~52 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 N/A53~56 1,5 1,5 1,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 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









DN09141912Issue 01


36 (36 (45)))


HSUPAdata UEs

perHSUPA

scheduler


24.6 26.1 27.5 29 30.4 31.9


2 N/A N/A N/A N/A N/A N/A3~4 N/A N/A N/A N/A N/A N/A

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




















HSUPAdata UEs

perHSUPA

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

45~48 N/A N/A N/A N/A N/A N/A N/A49~52 N/A N/A N/A N/A N/A N/A N/A














DN09141912Issue 01


38 (38 (45)))

In Table 5, Table 6 , Table 7 and Table 8 , the assumption is that the HSUPA licensedcapacity is limited, as well as the typical use case when the majority of the users are DLdata dominated and the remaining users are UL data dominated.

In Table 5 , Table 6 , Table 7 and Table 8 , the assumption is that 16QAM is not used.

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

Number of HSUPA 16QAM transmittingUEs

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 transmitswith 16QAM modulation. While in the second TTI, different modulation can be useddepending 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 one16QAM 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/2msTTI/10msTTI users, 16QAM transmitting users and CS Voice over HSPA), the followingrule 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:

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

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

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





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

16QAM_2msTTI_Subunits – subunits required for UEs simultaneouslytransmitting with 16QAM modulation (note that only UE in good radio conditionand appropriate amount of data in buffer is able to use 16QAM transmission).

CS_Voice_over_HSPA_Subunits – subunits required for CS Voice over HSPAusers.

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.3Mbpsthroughput;

F-DPCH_2msTTI_Subunits – 0.625 subunits required; see Table 7 (8users, 5.8Mbps combined L1 thr);

F-DPCH_10msTTI_Subunits – 0.5 subunits required; see Table 5 (10users, 2.9Mbps combined L1 thr);

No-F-DPCH_2msTTI_Subunits – 0.5 subunit required; see Table 8 (9users, 4.3Mbps combined L1 thr);

No-F-DPCH_10msTTI_Subunits – 0.75 subunits required; see Table 6 (15 users, 4.3Mbps combined L1 thr);

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.




DN09141912Issue 01


40 (40 (45)))

HSUPAUEs perHSUPA

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

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 isrecommended. Interference cancellation is performed with PIC pool unit. With thecommissioning parameter, the operator can activate one PIC pool unit providinginterference 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 packet of data Cell_FACH stateusing transmission on HSUPA and HSDPA channels (UL/DL). UE in Cell_FACH statedoes not require any capacity license.

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

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

However, if operator wants to guarantee certain amount of baseband resources for HSCell_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 stepbaseband capacity

reservation0.125 subunit

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 HSPAusers can be allocated in one subunit.

Number of CS Voice over HSPAusers Flexi Lite BTS

10 0.125

20 0.25

30 0.375

40 0.5

50 0.625

60 0.75




DN09141912Issue 01


42 (42 (45)))

70 0.875

80 1 Table 12 CS Voice over HSPA users

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 theHSUPA license (HSUPA processing set) and the HSDPA license (HSDPA processingset).

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

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

4.7 E-TFCI table selection

E-DCH Transport Format Combination Indicator (E-TFCI) corresponds to single TransportBlock Size (TBS) transmitted within E-DPCH in single TTI. E-TFCI table is a set of TBSs,

which can be selected for E-DCH transmission. In case of 10ms TTI transmission, 3GPPdefines two E-TFCI tables:

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

In case of 10ms TTI transmission with configured F-DPCH channel (RAN1201 FractionalDPCH ), it is recommended to use E-TFCI Table 1. Otherwise, if E-TFCI Table 0 isconfigured for 10ms TTI HSUPA users with F-DPCH channel, the amount of HSUPAusers in baseband gets limited. 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 withE-TFCI Table 0 is affected, as in this case user consumes more baseband resourcesthan a user with E-TFCI Table 1. As a result, fewer resources are available for high datarate users.

In case of low data rates (single Mac-d PDU) and E-TFCI Table 0, the smallest physicalchannel for sending one MAC-d PDU in a TTI is limited to Spreading Factor 16 (SF16). Itis limited by coding rate, which has constant threshold value in 3GPP. E-TFCI Table 1allows usage of physical channel SF32. Physical channel SF16 requires roughly doublebase band resources compared to SF32. Thus, it has direct impact on the amount ofusers that can be allocated.

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

To configure E-TFCI Table 1 in case of 10ms FDPCH E-DCH transmission, RNC PRFILEparameter 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 twentyfour users and the available throughput by 5.8Mbps. For example, if two HSUPA BTSprocessing sets were bought, then up to 2x5.8Mbps = 11.6Mbps throughput will besupported and up to 2x24 users = 48 users. Note that also an ASW license might beneeded to reach a certain throughput.

In WN8.0, the HSUPA BTS Processing Set allows reaching up to 5.8Mbps throughputand up to 24 users simultaneously. To calculate the required number of HSUPA BTSprocessing 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 HSPAusers)

HSUPA_data_users_throughput – is combined HSUPA throughput (data + CSVoice 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 scenarioassumptions.




DN09141912Issue 01


44 (44 (45)))

5 Multi RAB

Multi RAB call is a single user call with multiple (up to four) services (RABs) activesimultaneously. For example UE actively downloading data via HSDPA service whilehaving simultaneous AMR voice call, has a Multi RAB service with two RABs established:HSDPA RAB + AMR RAB. General classification of Multi RAB calls is as follows:

HSDPA + AMR call;

HSUPA + AMR call;

HSUPA/HSDPA + HSUPA/HSDPA call;

DCH + DCH call;

For more specific information about MultiRAB calls, see WCDMA RAN BTS RRM HSDPA

and WCDMA RAN BTS RRM HSUPA document.

5.1 HSDPA + AMR call resource allocation

If UE has active HSDPA service (UL: Rel.99, DL: HSDPA) while AMR on DCH service isestablished, resources for the AMR service need to be allocated.

5.2 HSUPA + AMR call resource allocationIf AMR DCH service is established while UE has an active HSUPA service (UL:HSUPA,DL: HSDPA), the AMR service is processed with already allocated HSUPA resources.

AMR service of Multi RAB call does not require any additional baseband resources forprocessing, neither Rel99 CE licenses in UL/DL are required.

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

- HSPA non-FDPCH connection: the newly established AMR service of Multi RABcall is not having any impact on available baseband resources;

- HSPA FDPCH connection: if AMR service of Multi RAB call is newly set up, theHSUPA connection is considered as HSUPA non-FDPCH from the basebandresource consumption point of view.

5.3 HSUPA/HSDPA + HSUPA/HSDPA callresource allocation

Each HSUPA/HSDPA service of a Multi RAB call requires UL/DL baseband resources forprocessing. One UE with Mutli RAB service counts as one UE from HSUPA and HSDPAProcessing 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 consideringHSUPA license (user count) point of view. Adequately, in case of HSDPA ProcessingSets, 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 inUL/DL for processing. In case of Multi RAB call, equivalent amount of R99CEs isconsumed as in case of separate DCH Single RAB calls.

Rel99 CE licenses for each DCH service in Multi RAB call are required according tobearer rate. For example, 64/64kbps + 64/128kbps Multi RAB baseband resourcereservation is the same with baseband resource reservation for 64/64kbps and64/128kbps Single RABs.

ru40 flexi lite bts baseband dimensioning guidelive

Documents