05 rn31545en30gla0 capacity dimensioning

RN31545EN30GLA0

Radio Interface Capacity Dimensioning

1

1 Nokia Siemens Networks CN31545EN30GLA0

Course Content

WCDMA & HSPA fundamentalsRadio network planning fundamentalsRadio network planning processCoverage dimensioningCapacity dimensioningCoverage & capacity planningCoverage & capacity improvementsNSN radio network solutionSite Solutions & Site PlanningInitial Parameter Planning

RN31545EN30GLA0


2


Module Objectives

At the end of the module you will be able to: Understand basic traffic modeling Calculate air interface capacity & load

RN31545EN30GLA0


3


Air Interface Capacity Dimensioning

Traffic estimate & model Air interface dimensioning

DCH load calculation HSDPA capacity HSUPA capacity R

adio

net

wor

kA

cces

s ne

twor

k

Note:- This Learning Element contains the Air Interface dimensioning- The dimensioning of Channel Elements (CE) can be found in the proceeding Learning Element- Iux & RNC dimensioning can be found in RN3003 3G IP Transmission Planning & similar courses

RN31545EN30GLA0


4


Traffic estimation

The traffic estimation requires information related to the network topology, subscribers & traffic: Cell Area from Coverage Dimensioning Subscriber density from Marketing Subscriber traffic profile from Marketing

Subs densityCell area Traffic / subscriber

Traffic / cell

Traffic / site

RN31545EN30GLA0


5


Subscriber density

Operator subscriber density depends on: Population density Mobile phone penetration Operator market share

The subscriber density can be considered quite stable in mature markets Mobile phone penetration close to 100% for basic services Major changes possible only when new operators come to the market or with aggressive marketing

campaigns

In developing markets fast changes in mobile phone penetration and operator market share

RN31545EN30GLA0


6


Traffic information

The subscriber density & Subscriber traffic profile are the main requirements for capacity dimensioning

Traffic forecast should be done by analysing the offered Busy Hour traffic per subscriber for different services in each rollout phase

Traffic data: Voice :

Erlang per subscriber during busy hour of the network Codec bit rate, Voice activity

Video call : Erlang per subscriber during busy hour of the network Service bit rates

NRT data : Average throughput (kbps) per subscriber during busy hour of the network Target bit rates

RN31545EN30GLA0


7


Example: Subscriber traffic profile / traffic estimation

Subscriber traffic profile - Marketing Forecast (Example)(Average) traffic demand per subscriber in busy hour: Speech telephony: 20 25 mErl Video telephony: 2.5 3.0 mErl SMS 0.3 Data services ~ 600 1000 bps (DL), ~ 75 - 100 bps (UL)

Traffic Estimation (Example) Coverage Area (Site): 10 km2

Planning Area: 100 km2 & 10 000 subscribers 100 subs/km2 1000 subs/Site User profile

Speech traffic: 25 mErl/subs/BH NRT data traffic: DL 750 bps/subs/BH, UL 75 bps/subs/BH

Site traffic: Speech - 25 Erl/cell/BH +NRT data DL - 750 kbps/cell/BH,NRT data UL - 75 kbps/cell/BH

RN31545EN30GLA0


8


Traffic model: Erlang B

Traffic model is used to derive the required capacity from average traffic & service quality requirement

RT traffic (speech, video call, video streaming) is commonly modelled with Erlang-B model Average traffic (Erlangs) A Blocking probability (%) B required No. of traffic channels N

NRT traffic (web, email services) can be modelled as average traffic with defined overhead

N= number of

TrunksA Trafficcarried

TrafficLost

B

RN31545EN30GLA0


9


Erlang-B model

Erlang-B model is used for a system without queuing

Assumes random call arrival The Blocking probability B can

be calculated as

A = traffic in Erl N = required number of traffic

channels

1% 2% 3% 4% 5% 6% 7% 8% 9% 10%5 11 10 10 9 9 9 9 8 8 86 13 12 11 11 10 10 10 9 9 97 14 13 12 12 11 11 11 10 10 108 15 14 14 13 13 12 12 12 11 119 17 15 15 14 14 13 13 13 12 12

10 18 17 16 15 15 14 14 14 13 1311 19 18 17 16 16 15 15 15 14 1412 20 19 18 18 17 17 16 16 15 1513 22 20 19 19 18 18 17 17 16 1614 23 21 21 20 19 19 18 18 17 1715 24 23 22 21 20 20 19 19 18 1816 25 24 23 22 21 21 20 20 19 1917 27 25 24 23 22 22 21 21 20 2018 28 26 25 24 23 23 22 22 21 2119 29 27 26 25 24 24 23 23 22 2220 30 28 27 26 26 25 24 24 23 2321 31 29 28 27 27 26 25 25 24 2422 32 31 29 28 28 27 26 26 25 2523 34 32 30 29 29 28 27 27 26 2624 35 33 32 31 30 29 28 28 27 2725 36 34 33 32 31 30 29 29 28 2826 37 35 34 33 32 31 30 30 29 2927 38 36 35 34 33 32 31 31 30 2928 39 37 36 35 34 33 32 32 31 3029 40 38 37 36 35 34 33 33 32 3130 42 39 38 37 36 35 34 34 33 3231 43 41 39 38 37 36 35 35 34 3332 44 42 40 39 38 37 36 35 35 3433 45 43 41 40 39 38 37 36 36 3534 46 44 42 41 40 39 38 37 37 3635 47 45 43 42 41 40 39 38 38 3736 48 46 44 43 42 41 40 39 39 3837 49 47 45 44 43 42 41 40 40 3938 51 48 46 45 44 43 42 41 40 4039 52 49 47 46 45 44 43 42 41 4140 53 50 48 47 46 45 44 43 42 4241 54 51 50 48 47 46 45 44 43 4342 55 52 51 49 48 47 46 45 44 4343 56 53 52 50 49 48 47 46 45 4444 57 55 53 51 50 49 48 47 46 4545 58 56 54 52 51 50 49 48 47 4646 59 57 55 53 52 51 50 49 48 4747 61 58 56 54 53 52 51 50 49 4848 62 59 57 55 54 53 52 51 50 4949 63 60 58 56 55 54 53 52 51 5050 64 61 59 57 56 55 54 53 52 51

N = required No. of trunks

B = Blocking Probability

=

=

N

i

i

N

iA

NA

ANB

0 !

!),(

A = Average traffic [Erl]

RN31545EN30GLA0


10


Packet data modelling

Packet data traffic is a sum of multiple services with different traffic profiles and service quality requirements

Accurate modelling of packet data traffic requires multiple assumptions and complex simulations

Practical packet data traffic model utilises average bit rate with fixed overhead for protocol and QoS

The overhead can assumed to be 27% This figure includes the L2 re-transmission overhead of 10% and 15% of buffer

headroom to avoid overflow (peak to average load ratio headroom) (1+0.10) x (1+0.15) = 1.265 26.5% overhead

Required bit rate = (1 + Overhead) * Average bit rate

Overhead here means the excessive data to be sent with original one.

RN31545EN30GLA0


11


Example: Traffic models

Cell traffic: 25 Erl/cell/BH, 750 kbps/cell/BH

Speech: 25 Erl & 2% blocking 34 traffic channels

NRT data DL: 750 kbps * (1 + 26%) = 945 kbps

NRT data UL: 75 kbps * (1 + 26%) = 94.5 kbps

assumed overheadfor protocol & QoS

10% L2 re-transmission overhead15% buffer headroom to avoid overflow(1+0.10) x (1+0.15) = 1.265 26.5% overhead

RN31545EN30GLA0


12




DCH load calculation HSDPA capacity HSUPA capacity Ra

dio

netw

ork

Acc

ess

netw

ork

RN31545EN30GLA0


13


Cell load calculation is needed in order to estimate the level of air interface load in the cell

Air interface load depends on service mix, radio propagation conditions, network topology and number of active connections as well as traffic inputs or load estimation

Service type Bitrate, Eb/N0 Propagation conditions Eb/N0, Orthogonality Network topology Little i (other cells Interference / own cell Interference

Air interface load Link budget

Cell rangeMax

. pathlo

ssCoverage Area

Load/cell Load estimation Traffic inputs

Load Calculation Introduction

RN31545EN30GLA0


14


Air interface capacity

WCDMA air interface capacity can be estimated with system simulations and/or analytical load calculations

System simulations provide a complete system model and possibility to model system specific parameters and network layout

Complex tools, not feasible to use for dimensioning Dimensioning can be done with pre-analysed results Limited possibility to change

system parameters

Analytical models utilise system and environment specific input parameters and simple models

Simple analysis can be done as part of dimensioning process Parameters configurable flexible model Results rely on realistic input parameter values

RN31545EN30GLA0


15


Load Calculation: Uplink Load

( ) jjbj

j

NERWL

1

//

1

1

0

+

=

=

=

N

jjUL L

0

j: Activity factor; for Speech some 67% due to VAD/DTX; for Data: 1

Load Ljof subscriberwith Service j

ULtotal

Cell Load

Activity Factor

Processing Gain

0

2

4

6

8

10

12

14

16

18

10 20 30 40 50 60 70 80 90 95 98

loading/%

loss

/dB

Inte

rfere

nce

Mar

gin

[dB]

UL = 30 50 %

Cell Load [%]

Load Calculation Formulas in analogy toH. Holma WCDMA for UMTS

The activity of a single bearer for example depends on the service used. If a bearer is used for a download using FTP, the activity is considerable higher in comparison to, for example, web browsing. With an FTP service running, the activity can be close to 100%, whereas with web browsing it can be 20%. Usually, the higher the peak rate of the connection, the lower is its activity.

RN31545EN30GLA0


16


Inter-Cell Interference: Little i

In the real environment we will never have separated cell. Therefore, in the load factor calculation the other cell interferences should be taken into account.

This can be introduced by means of the Little i value, which describes how much two cells overlap (bigger overlapping more inter-cell interferences)

Iown

Iother

ceinterferen cellown ceinterferen cellother

=i

Inter-Cell Interference RatioLittle i

( )

+

+=+=j

jjb

jjjUL

NERWiLi

1

//

1

1)1()1(

0

RN31545EN30GLA0


17


Uplink Load calculation

Simplified UL load equation UL DCH capacity for 1 service type j only W/Rj >> (Eb/No)j

Nj: No. of Trunks Nj x Rj = Cell Throughput = Capacity [kbps]

j

jbjjUL RW

NoENi

/)/(

)1( +=

RN31545EN30GLA0


18


Downlink Load calculation

The DL capacity can be calculated in a similar manner as the UL capacity from the DL Load The equations are similar to those of the UL, except two modifications:

Soft Handover Overhead SHO_OH: an Overhead has to be integrated into the calculation due to Soft Handover; in this case two Node Bs require capacity to serve a single user

Orthogonality Factor : In the DL, the Intra-Cell Interference shouldbe theoretically Zero ( Orthogonality of Channelisation Codes); due to a loss of Orthogonality caused by Multipath transmission,the Orthogonality Factor has to be taken into account; j = [0 .. 1.0] propagation channel conditions

The DL orthogonality & i are different for each user and average values have to be used in DL load calculations

( )

+

++=j

jjb

jjUL

NERWiOHSHO

1

//

1

1)1()_1(

0

Cell Type Macro Cell 0.4 0.9

Micro Cell > 0.9

typically 50 75 %

No. of Trunks Nj &Cell Throughput Nj x Rj [kbps]

No. of Trunks Nj &Cell Throughput Nj x Rj [kbps]

RN31545EN30GLA0


19


Little i & SHO overhead

The level of interference received from neighbouring cells depends strongly on

Network layout (site locations, antenna directions & sectorisation)

Propagation environment (propagation slope)

SHO overhead is related to the cell coverage overlap & other cell interference level

Sectorization HBW SHO Overhead i = Iother/Iown1-sector omni 23% 58%

3-sector 90 34% 88%

3-sector 65 27% 66%

3-sector 33 26% 70%

4-sector 90 42% 109%

4-sector 65 31% 76%

4-sector 33 33% 86%

6-sector 90 53% 146%

6-sector 65 42% 105%

6-sector 33 32% 90%

HBW: Half Beam-Width

Interference received from neighbouring cellssimulated DL values

RN31545EN30GLA0


20


Load Calculation Examples

Load factor for different services has to be calculated separately, total load is then the sum of different services in the cell area

UL/DL single connection load examples are shown in the table below For example 50 % UL load means on average 50 speech users or about 9 64 kbits/s users/cell

in a 3-sector (1+1+1) configuration

Services UL Fractional Load DL Fractional Load12.2 kbit/s 0,97% 1,00%64 kbits/s 4,80% 6,21%128 kbits/s 8,56% 11,07%384 kbits/s 22,89% 29,59%Total Load 37,22% 47,87%

RN31545EN30GLA0


21


Total WBTS DL power R99 traffic

Total DL base station transmit power can be a limiting factor in highly loaded cell

( )DL

CCCHN

jjSERVj

j

jbN

DL

TOTDL

PLRWNE

PP

+

= =

111

1,

0

where,

Lserv is the pathloss of user j. The pathloss is defined as total loss from BTS transmitter to the receiver

PCCCH is the total common control channel power

RN31545EN30GLA0


22


Example - Total DL power & load

Total DL power increases exponentially towards 100% of load Common control channels CCH consumes larger part of DL power

4 W CCCH & 50% load Total power 10.5 W 8 W CCCH & 50% load Total power 18.5 W

PtxTotal with different common channel power

4.0 4.3 4.7 5.05.4 5.9 6.4

7.0 7.78.5 9.4

10.511.8

13.415.4

17.9

21.3

26.0

33.1

8.0 8.5 9.19.7 10.3

11.111.912.9

14.015.3

16.718.5

20.623.1

26.3

30.4

35.9

0.0

5.0

10.0

15.0

20.0

25.0

30.0

35.0

40.0

0% 5% 9% 14%

18%

23%

27%

32%

36%

41%

45%

50%

54%

59%

64%

68%

73%

77%

82%

86%

91%

Downlink DCH load

PtxT

otal 4 W

8 W

RN31545EN30GLA0


23


Example: Load calculation

Is it possible to transmit 34 speech channels in one cell simultaneously with 945 kbps NRT DL data and 94.5 kbps NRT UL data?

Speech: 34 traffic channels NRT data: DL = 945 kbps, UL = 94.5 kbps

Fractional load of 12.2 AMR speech: DL Load = 34 * 1.0% = 34%, UL load = 34 * 0.97% = 33 %

Fractional load of NRT data (NRT 128 kbps): DL Load = 750 kbps/128 kbps * 11.07% = 64.9 %, UL Load = 75 kbps/128 kbps * 8.56% = 5.0 %

total DL load = 97.9% total UL load = 38% DL overload!

RN31545EN30GLA0


24


Example: Capacity analysis

How much DL traffic (in kbps) is possible for a max. allowed DL load of 74% simultaneously with 25 speech calls ?

Speech traffic of 25 Erlangs corresponds average of 25 calls in the cell Average speech load: UL = 24%, DL = 25%

Max. cell power 20 W with 2 W pilot allows max. DL load of 74% in the example cell

In average 49% load margin available for NRT data in DL 49% / 11.07% * 128 kbps = 566 kbps

In average 566 kbps DL available for NRT data

RN31545EN30GLA0


25





dio

netw

ork

Acc

ess

netw

ork

RN31545EN30GLA0


26


HSDPA dimensioning can be done based on: Requirement to achieve min. HSDPA cell edge throughput

Determined from link budget analysis, SINR at cell edge Requirement to achieve average HSDPA throughput across the cell

Determined by SINR distribution analysis

HSDPA capacity depends on: Available power for HSDPA Channel conditions Cell range (pathloss) Interference level over cell area HSDPA features

& configuration

SINR: Key measure forHSDPA Peak Data Rate /

Throughput

HSDPA Capacity Introduction / SINR

Geometry Factor

Total Transmit Power

Spreading Factor

Orthogonalityfactor

Transmitted HS-PDSCH

power

+

=

GP

PSFSINRtot

PDSCHHS

1116

Geometry Factor G = own Cell Interference / (other Cell Interference + Noise)

SINR: Signal-to-Interference+Noise Ratio

RN31545EN30GLA0


27


SINR & HSDPA Throughput

The single-user HSDPA throughputversus its average HS-DSCH SINR is plotted.

Notice that these results include the effect of fast fading & dynamic HS-DSCH link adaptation (and HARQ).

An average HS-DSCH SINR of 23 dB is required to achieve the maximum data rate of 3.6 Mbps with 5 HS-PDSCH codes

Benefit from using more codes (10/15) is only experienced for higher SINR values >10 dB

Aver

age

single

-use

r thr

ough

put [

Mbp

s]

Average SINR (1 HS-PDSCH) [dB]

0.5

1.0

1.5

2.0

2.5

-10 -5 50 10 15 20 25 300

3.0

3.5

4.0

HS-DSCH POWER 7W (OF 15W), 5 CODES, 1RX-1TX, 6MS/1DB LA DELAY/ERROR

Rake, Ped-A, 3km/hRake, Veh-A, 3km/hRake, Ped-B, 3km/hMMSE, Ped-A, 3km/hMMSE, Ped-B, 3km/hRake, Veh-A, 30km/h

Average HS-DSCH SINR [dB]Average SINR [dB]

Common cell edge condition

Inside macro

cell

Micro cell, LOS, low interference

Cel

l Thr

ough

put [

Mbp

s]

RN31545EN30GLA0


28


HSDPA throughput Orthogonality Close to the BTS the own cell interference

dominates (1/G i 0.9 can be achieved: in isolated environment Micro- / Pico- / Femto- Cells

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1

0 1000 2000 3000 4000 5000 6000 7000 8000 9000

Throughput, kbps

Ort

hogo

nalit

y

10% BTS pow er for HSDPA 50% BTS pow er for HSDPA

80% BTS pow er for HSDPA

( )

116 totPDSCHHS

PPSFSINR

for 1/G i

RN31545EN30GLA0


29


HSDPA Capacity: HSDPA power

Dynamic Resource Allocation feature: BTS can allocate all unused DL power to HSDPAAll the power available after DCH traffic, HSUPA control channels & common channels can be used for HSDPA

HSDPA power is shared dynamically between HS-SCCH & HS-PDSCH

Time

Power

PtxHSDPA = PWBTS_max PccH_tx - PDCHPHS-PDSCHs = PtxHSDPA PHS-SCCH

RN31545EN30GLA0


30


HSDPA Capacity G-Factor

The G Factor reflects the distance between the MS & BS antenna thus setting a value for G factor means making assumptions on user location.

A typical range is from -5dB (Cell Edge) to 20dB Typical G factor distributions (CDF) coming from NSN simulation tools as well as operator field

experience are represented in the following chart:

+

=

GP

PSFSINRtot

PDSCHHS

1116

-20 -10 0

G-factor [dB]

Cum

ulat

ive

dist

ribut

ion

func

tion

[%]

10 20 30 400

10

20

30

40

50

60

70

80

90

100

Macrocell(Wallu)Veh-A/Ped-A

Macrocell(Vodafone)Veh-A/Ped-A

Microcell(Vodafone)Ped-A

noiseother

own

PIIG+

=

Note: G=1/i in interference limited situations.

RN31545EN30GLA0


31


Cell size & HSDPA cell throughput

Cell size has an effect on HSDPA cell throughput when cell edge pathloss is high (large cell or indoor users)

Increase of BTS power has only limited effect on cell throughput

0

200

400

600

800

1000

1200

1400

100 105 110 115 120 125 130 135 140 145 150 155 160

Cell e dge pathloss , dB

HSD

PA c

ell t

hrou

ghpu

t

DCH load 10%&20W

DCH load 30%&20W

DCH load 50%&20W

DCH load 10%&40W

DCH load 30%&40W

DCH load 50%&40W

5 codes

RN31545EN30GLA0


32


HSDPA capacity & Code Multiplexing

HSDPA capacity is influenced by the capabilities of the network and the UE Number of codes (5, 10, 15) Higher peak bit rate in good conditions Higher cell throughput Code multiplexing: multiple 5 code UEs can utilise up to 15 codes Higher spectrum efficiency

1.2 Mbps

1.7 Mbps

1.8 Mbps

2.0 Mbps

2.2 Mbps

5 Codes

Cell capability

10 Codes 15 Codes

no code-multiplexing (10/15 code UEs)

code-multiplexing (5 code UEs)

RN31545EN30GLA0


33


HSDPA Capacity: RU20 features

RU20 features improving the HSDPA capacity: 64QAM 2x2 MIMO DC-HSDPA CS Voice over HSPA

64QAM

max. Peak Rate = 21 Mbps good channel conditions required to take benefit of 64QAM CQI 26 !

64QAM requires 6 dB higher SNR than 16QAM average CQI typically 20 in the commercial networks

DC-HSDPA:1) Improved Load Balancing 2) Frequency Selectivity3) Reduction of Latency 4) Higher Peak Data Rates 5) Improved Cell Edge User Experienced

10 MHz1 UE, using 2 RF

Channels:Peak Rate =

2 x 21 Mbps =42 Mbps

F1 F2

5 MHz 5 MHz

10 % pilot power0.8 dB safety margin removed from the max. PA powerAverage pathloss 133 dB

RN31545EN30GLA0


34



2x2 MIMO: Single- or Dual-stream Operation max. Peak Rate = 28 Mbps

Legacy HSDPA

Cell edge:low SINR

High SINR

Single-streamMIMO

Dual-stream MIMO

Mea

n C

ell T

hrou

ghpu

t [M

bps]

UE

Thr

ough

put (

PF)

[kbp

s]

SISO: Single Input Single Output RxDiv: Receive Diversity: 1 Tx-, 2 Rx- Antenna(s) CLM1 2x2: Closed Loop Mode; Single-Stream with Rx- & Tx-Diversity MIMO 2x2: Dual-Stream MIMO using Spatial Multiplexing

RR: Round RobinPF: Proportional FairPF-RAD-DS: PF scheduling extended by Required Activity Detection with Delay Sensitivity


RN31545EN30GLA0


35



Voice over HSPA

Assumed IP Header

Compression

HS-DSCH

E-DCH

for Voice, SRB & other services


RN31545EN30GLA0


36





dio

netw

ork

Acc

ess

netw

ork

RN31545EN30GLA0


37


HSUPA Capacity HSUPA Cell Throughput

Principle: Example ( Diagram) max. Load for HSUPA higher than for Rel. 99 DCH* UL(HSUPA) = 80%1) UL load is shared between HSUPA & R99 DCH users Rel. 99: 50% Load

HSUPA: 80% - 50% = 30% Load2) UEs distribution inside the cell has impacts on possible C/I; impacts on cell throughput

here: each UE is allocated an equal share of UL Load LHSUPA_UE = 30% / 5 UE = 6%

* due to Fast Packet SchedulingLHSUPA_UE: Load per UE

0

2

4

6

8

10

12

0 20 40 60 80 100

Uplink Load (%)

Incr

ease

in In

terfe

renc

e (d

B)

Example Target Uplink Load

UL Load generated by R99 DCH

UL Load available for HSUPA UE

RN31545EN30GLA0


38


( )iIC

Nj

j

jj

UL ++

= ==

1

)/(11

11

HSUPA Capacity HSUPA Cell Throughput

3) UL load is translated to UL C/I using the UL load equation

C/I: Chip-Energy/Interference= Eb/No Processing Gain* Example: i = 0.65; j(data) = 1

LHSUPA_UE = 6% = (1+ i) / ( 1 + 1 / C/I)

C/I = 1/((1+i)/LHSUPA_UE -1) = 0.051 = - 12.9 dB

4) C/I is translated to HSUPA bit rateusing the Eb/No look-up table

derived from link level simulations

* both in dB; decimal: (Eb/No) / (W/R)

Layer 1 Bit Rate

TTI (ms)

Physical Channel

Eb/No with RxDiv W/R C/I

1920.0 10 2*SF2 0.5 dB 3 dB -2.5 dB

1440.0 10 2*SF2 0.1 dB 4.26 dB -4.16 dB

1024.0 10 2*SF2 0.2 dB 5.74 dB -5.54 dB

512.0 10 2*SF4 0.6 dB 8.75 dB -8.16 dB

384.0 10 1*SF4 0.9 dB 10 dB -9.1 dB

256.0 10 1*SF4 1.1 dB 11.76 dB -10.66 dB

128.0 10 1*SF8 1.9 dB 14.77 dB -12.87 dB

30% HSUPA Load 5 x 128 kbps total

RN31545EN30GLA0


39


HSUPA Capacity: Example

HSUPA average cell throughput vs. Rel. 99 DCH loadH

SUP

A ce

ll th

roug

hput

[kbp

s]

Example: HSUPA Load = 30%HSUPA throughput = 5 x 128 kbps

Assumptions: Activity = 100%, Little i = 0.65

RN31545EN30GLA0


40



Summary

The Air Interface Capacity dimensioning includes aspects:

Traffic estimation & modelling

Air Interface Load estimation Rel. 99 / HSDPA / HSUPA Capacity for each carrier (shared Rel. 99/HSPA or dedicated HSPA)

Capacity strongly depends on: Interference: Inter-Cell Interference i, SINR Orthogonality factor Quality Requirements Eb/No Power (total Power / HSPA Power)

05 rn31545en30gla0 capacity dimensioning

Documents

subscribers traffic

offered busy hour traffic

basic traffic modeling

rollout phase traffic

network target

network service

network codec

network topology