01 RN31521EN40GLA0 Baseband Dimensioning RU40 v3

HSUPA resources allocation (1/2) •

HSUPA scheduler supports different types of HSUPA users (2msTTI/10ms TTI, F-DPCH/no-FDPCH, CS Voice over HSPA users)

• •

Each type of HSUPA user has different baseband require ments

•

For HSUPA scheduler baseband resources dimensioning purpose few different tables according to the user types should be used

•

CS Voice over HSPA users consume Subunits. Max 18 CS Voice over HSPA users are allocated in single Subunit

Required Baseband resources for HSUPA scheduler depends on number of CS Voice over HSPA and HSUPA active users and combined L1 throughput

10ms TTI no-FDPCH dimensioning table 10ms TTI FDPCH dimensioning table 2ms TTI FDPCH dimensioning table 2ms TTI n o-FDPCH dimens ioni ng table #CS Voice over HSPA users

HSUPA scheduler baseband resour ces fo r CS Voice over HSPA and HSUPA data us ers

HSUPA subunits for CS Voice over HSPA users Baseband consumptio n • CS Voice over HSPA users consume Subunits. Consumption depends on selected TTI o

2ms TTI: Up to 18 CS Voice over HSPA users can be allocated in one Subunit

o

10ms TTI: Up to 40 CS Voice over HSPA users can be allocated in one Subunit

Numb er of 2ms TTI CS Voice over HSPA users

Subunit

Number of 10ms TTI CS Voice over HSPA users

Subunit

10

0.25

4

0.25

20

0.5

9

0.5

30

0.75

13

0.75

40

1

18

1

•

Each CS Voice over HSPA user decreases the maximum number of HSPA users allowed by HSDPA and HSUPA scheduler user pool.

•

CS Voice over HSPA user does not consume Rel99 CE licenses. Each CS Voice over HSPA user decreases the throughput and the number of users allowed by the HSUPA Processing Set and the HSDPA Processing Set.

•  A CS Voice over HSPA user (as a regular HSPA user) has the same priority as HSPA user

HSUPA dimensioning (1/2) RU40 BB resources reservation To calculate the subunits reservation inside System Module Rel.2 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:

HSUPA_Subun its = F-DPCH_2msTTI_Subun its + F-DPCH_10msTTI_Subun its + no-F-DPCH_2msTTI_Subunits + no-F-DPCH_10msTTI_Subunits + CS_Voice_over_HSPA_Subunits + 16QAM_transmitting_Ues_subunits

Where: • F-DPCH_2msTTI_Subunits = subunits required for HSUPA F-DPCH 2ms TTI users • F-DPCH_10msTTI_Subunits = subunits required for HSUPA F-DPCH 10ms TTI users • No-F-DPCH_2msTTI_Subunits = subunits required for HSUPA no-F-DPCH 2ms TTI users • No-F-DPCH_10msTTI_Subunits = subunits required for HSUPA no-F-DPCH 10ms TTI users • CS_Voice_over_HSPA_Subunits – subunits required for CS Voice over HSPA users • 16QAM _transmitting_EUs_Subunits – subunits required for 16QAM transmitting UEs Note: in some cases presented rule may lead to overestimation of baseband resources

HSUPA dimensioning (2/2) RU40 HSUPA Processing Sets requirements • In order to reach simultaneously certain number of HSUPA users (data + CS Voice over HSPA) and certain combined L1 throughput , the following formula should be used to calculate required number of HSUPA BTS Processing Minim um amoun t of HSUPA BTS Processin g Sets = max ( Roundup ( Number_of_HSUPA_users / 24) ; Roundup(HSUPA_throughput / 5,8) )

Where: Number_of_HSUPA_users – Number of HSUPA users (data + CS Voice over HSPA) HSUPA_throughput – HSUPA users (data + CS Voice over HSPA) throughput [Mbps]

HSUPA BTS Processing Set resources allocation HSUPA us ers/throughp ut dist ributi on

•

 Available HSUPA BTS processing set resources needs to be distributed among HSUPA schedulers

•

 If HSUPA scheduler is present in both System Modules (same LCG), in this case BTS will allocate HSUPA licenses proportionally to baseband capacity for traffic use of each system module, with BTS processing set granularity.

•

 If Baseband pooling is used then BTS will divide HSUPA licenses between LCG’s according to commissioned share (HSUPA user/throughput license share). Sum of LCG shares is always 100%. HSUPA licence share is performed with HSUPA BTS processing set licence granularity. If licenses cannot be share equally between LCGs, in that case BTS will divide higher amount of licenses to LCG starting from lowest LCG number. E.g.: if commissioned shares are 50% / 50% and there are 5 HSUPA licenses, then LCG1 gets 3 licenses an d LCG2 gets 2 licenses.

CCCH and R99 Dimensioning

Common Control Channels General information

•

Each System Module rel.2 contains CCCH processing resources included in System Module capacity, supporting basic configurations. DL

•

Processing of Common Control Channels might require certain amount of Rel99 CE.

1 x P-SCH 1 x S-SCH 1 x P-CCPCH

•

The amount of baseband resources allocated for CCCH processing depends on:

• Number of cells • Cell range • Number of signatures • with Number of Rx branches Cell radius higher than 20km is called

1 x P-CPICH 1 x PICH 1 x AICH 3 x S-SCCPCH

Extended Cell

UL PRACH

CCCH baseband allocation (1/4) CCCH requirements Each System Module Rel.2 provides processing resources for Common Control Channel for basic configurations like:

• •

 1 * System Module : 3 cells/20 km (e.g. 1+1+1 with 20 km cells)  1 * System Module : 6 cells/10 km (e.g. 2+2+2 with 10 km cells)

Therefore having 2 System Modules rel.2 (e.g. FSMD + FSME) the following configurations are covered with CCCH resources included in System Modules rel.2 capacity:

• • •

 2 * System Module: 6 cells/20 km (e.g. 2+2+2 with 20 km cells)  2 * System Module: 9 cells/10 km (e.g. 3+3+3 with 10 km cells)  2 * System Module: 12 cells/10 km (e.g. 4+4+4 with 10 km cells)

CCCH proc essing resou rces inclu ded in singl e System Module rel.2 capacity can be used only for by one LCG LCG 1: 3cell/10km, LCG1: 6cell/10km

LCG 1: 3cell/10km, LCG 2: 3cell/10km

48 Rel.99 CE requir ed for LCG2

LCG 2: 3cell/10km

CCCH baseband allocation (2/4) CCCH requirements In certain cases if longer cell radius or higher number of cells is preferred, more Rel99 CE capacity may need to be licensed: 1 * FSMC/D/E 6 cells/20 km: + 48 Rel.99 CE needed 9 cells/10 km: + 48 Rel.99 CE needed, 9 cells/20 km: + 96 Rel.99 CE needed 12 cells/10 km: + 48 Rel.99 CE needed, 12 cells/20 km: + 144 Rel.99 CE needed

2 * FSMC/D/E 6 cells/20 km: + 0 Rel.99 CE needed 9 cells/10 km: + 0 Rel.99 CE needed, 9 cells/20 km: + 48 Rel.99 CE needed 12 cells/10 km: + 0 Rel.99 CE needed, 12 cells/20 km: + 96 Rel.99 CE needed

CCCH baseband allocation (3/4) CCCH requirements Other configurations that can be served with resources included in Release 2 HW System Modules or single pool of 48 Rel99 CE can be de termined with the formula below: # _ of  _ cells

∑ (Cell Rangei * # of Signaturesi * Rx) =< 480 i =1

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