Dimensioning Process: Pre-Planning Detailed Planning Post - Planning

Dimensioning process
MODULE 9
PREPLANNING
Dimensioning
Requirements
and strategy
for coverage,
capacity and
quality
PER SERVICE
Network
configuration
POSTPLANNING
DETAILED PLANNING
Configuration
Planning
Coverage and Capacity

Planning
Parameter
Planning
Post-launch
optimisation
Node-B
Configuration
Propagation measurements
Coverage prediction
Area/cell
specific
Measurement
surveys
Antenna line
configuration
Load estimation
Traffic distribution
Planned Service and QoS
definition
Handover
strategies
Statistical
performance
analysis
Site selection and planning
Pre-launch
optimisation
Power budget
Other RRM
PER SERVICE
Site acquisition
Measurements
Nokia Siemens Networks
Presentation / Author / Date
Quality
Efficiency
Availability
Objectives
After this module the participant shall be able to: Understand basic steps of dimensioning
To calculate cell loading
Module Contents
Summary of inputs
Capacity Calculation Method
Channel element (WSP) calculation
Module Contents
Summary of inputs
Dimensioning Process Description

Evaluate cell range using max system
load and link budget for user at the cell
edge
1.
Coverage limited max. cell

range for specified max
system load
Compute cell loading from

traffic profile and cell range
Decrease max
system load
Coverage Less
Limited than
Add Carrier/
Decrease cell radius
Greater
than
Planning threshold definition and Cell range

calculation Cell range
3.
Cell load and throughput calculation Cell

load, HSPA throughput
4.
Capacity evaluation
Compare cell loading with the

maximum permissible system load ?
Cell range known
R99 service link budget for selected service(s)

HSDPA link budget with selected cell edge
throughput
HSUPA link budget with selected cell edge
throughput
Initially with max. load
2.
Capacity
Limited
Equal to
Base station configuration selection and

power budget calculation for all limiting
services
Cell load Initial load
DL power Max. power
HSPA throughput Minimum throughput
Cell range&area Number of cells
Antenna height

edge
system load
Decrease
max system
load
Coverage Less
Limited than
Add Carrier/
Greater
than
Capacity
Limited

Equal to
Cell range known
Coverage limited scenario

System loading is lower than the level used
initially to compute the cell range
Rise in interference floor used in the link
budget calculation was pessimistic
Complete process is repeated with a lower

value of system loading
Lower increase in interference floor
greater cell range more users in each cell
greater actual system loading.
The reduction in system loading used in the

link budget calculation is continued until it
matches the actual system loading
computed by the traffic profile. This then
defines the final cell range.

Capacity limited scenario
edge
system load
Decrease max
system load
Coverage Less
Limited than
Add Carrier/
Decrease cell
radius
Greater
than
Capacity
Limited

Equal to
Cell range known
In this case
System loading is greater than the maximum

level used initially to compute the cell range
Maximum DL power is exceeded
HSPA throughput (UL or DL) is lower than

minimum throughput
Cell capacity must be increased or the cell

size decreased
Increase the cell capacity by adding additional
carriers
Dedicated HSPA carrier also possible
Reduced cell range

the cell
fewer users loading
A reduction in cell range is made and the

system loading re-calculated
The reduction in cell range is done iteratively

until the target load or HSPA throughput is
achieved. This then defines the final cell
range.
Module Contents
Summary of inputs
Input parameters overview

Input Categories
CAPACITY RELATED
CAPACITY RELATED
Spectrum Available
Spectrum Available
User Profile and Traffic
User Profile and Traffic
Growth Forecast
Growth Forecast
Traffic Density Map
Traffic Density Map
COVERAGE RELATED
COVERAGE RELATED
Coverage Regions
Coverage Regions
Area Type Information
Area Type Information
QUALITY RELATED
QUALITY RELATED
MS Class
MS Class
Indoor Coverage
Indoor Coverage
Location Probability
Location Probability
Blocking Probability
Blocking Probability
Gives an Estimation of the

Equipment
Gives an Estimation
Necessary of
tothe
Meet
Equipment
Necessary
to
the Network RequirementsMeet
the Network Requirements
Network Dimensioning
Activities
Network Dimensioning
Activities
Radio Link Budget
Calculation
Radio Link Budget
Calculation
Cell Size Calculation
Cell Size Calculation
Capacity Calculation
Capacity Calculation
Transmission Network
Estimate
Transmission Network
Estimate
Capacity Related Input

The number of subscribers, user profile and spectrum available are the main
requirements for capacity dimensioning
Traffic forecast should be done by analysing the offered Busy Hour traffic per
subscriber for different service bit rates in each rollout phase.
Traffic data:
Voice :
Erlang per subscriber during busy hour of the network
Codec bit rate, Voice activity
RT data :
Erlang per subscriber during busy hour of the network
Service bit rates
NRT data :
Average throughput (kbps) subscriber during busy hour of the network
Target bit rates
Asymmetry between UL an DL traffic for NRT Services (Downloading 1/10)

should be taken into consideration.
Network and Subscribers evolution forecast is also needed.
10
Capacity Related Input

The
Thetraffic
trafficfigures
figuresare
arebroken
brokendown
downinto
intotraffic
trafficper
per
subscriber
subscriberand
andbusy
busyhour
hourfor
foreach
eachservice,
service,separately
separatelyfor
for
uplink
uplinkand
anddownlink
downlink
Asymmetry
11
HSPA related dimensioning inputs

Required cell edge throughput (HSDPA and HSUPA) is required for the
power budget calculation
HSPA coverage
The required HSPA capacity inputs can be given as

Required total cell throughput
OR
HSPA traffic profile per user as in R99 traffic Total required throughput
Maximum total DL power for HSDPA and max UL load for HSUPA has to
be defined
12
Coverage Related Input

Area type information must be as accurate as possible:
coverage area for each rollout phase
percentage of the area for each morpho-class (DU,U,SU,R)
building penetration loss and fading margin
MorphoClass Build Pen Loss
Dense Urban
Urban
Sub Urban
Rural
Road
18 dB
15 dB
12 dB
10 dB
Stand Deviation
Car Loss
Stand Deviation
6 dB
7 dB
11 dB
10 dB
9 dB
9 dB
propagation models for path loss calculation

correction factors for the Propagation Model
Service Scenarios should be defined: which kind of service is to be offered and

where
Target coverage area and Coverage Probability for each service type
13
Quality Related Input

The network dimensioning is focused on fulfilment quality expectations
form user point of view. It means that resources should be as efficient as
demanding(QoS) are service requirements in dimensioned network.
Blocking Probability is blocking of call attempts due to lack of available
resources and for CS Services is usualy between1-2%
In cellular networks the coverage areas of cells overlap and the mobile
station is able to connect to more than just one serving cell. If more than
one cell can be detected the location probability increases and is higher
than determined for single isolated cell. Location probability usually is
within the range 90 99%. It depends on environment, service and
customer requirements and has a big impact on the number of site
probability density
x
Local
Localcoverage
coverageprobability:
probability:
PPcov (b,x)
= P [ F(x) > F
cov (b,x) = P [ F(x) > F
]
threshold
threshold]
14
F threshold
F median
(x)
received signal level [dBm
Module Contents
Summary of inputs
15
Cell Loading Calculation

edge
system load
traffic profile and cell
range
1.
R99 traffic load calculation
2.
Total DL power calculation
3.
HSDPA throughput calculation
4.
Decrease max
system load
CoverageLess
Limited than
Add Carrier/
Greater
than
Capacity
Limited

Equal to
Cell range known
16
Available DL power for HSDPA
HSUPA throughput calculation
Available UL load for HSUPA
Cell Loading Calculation R99 traffic

1. Traffic per Cell
Erlang or kbit/s
Traffic per cell is usually defined in terms of Erlang for voice

and real time (RT) data services and in terms of kbits/s for non
real time (NRT) data
2. Traffic Channels
For voice and RT data services the calculations are based upon
the Erlang B formula and for NRT data services upon
throughput. The two equations are given below.
3. Physical Channels
(=traffic channels*SHO)
Voice and RT data:

4. Interfering Channels
(=physical channels*activity factor)
5. Fractional Load
17
NRT data:
tchs ErlangBchs(bloc _ prob; traffic )

tchs
traffic
throughput * R
R is the service bit rate. The blocking probability is typically

assumed to be 2%. The throughput is assumed to be 79%. 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
=> throughput 79%

Evaluation of the physical channel requirement per carrier for
each service class. This is completed separately for UL and DL.
1. Traffic per Cell

Erlang or kbit/s
In the case of the UL,
tchs
ph _ chs
carriers
2. Traffic Channels
5. Fractional Load
Initially a single carrier is assumed. This is later increased if there is

need to do so for capacity reasons.
In the case of the DL,
tchs (1 Soft _ HO _ oh)

ph _ chs
carriers
Evaluation of interfering channels per cell for each service class.

This requires a direct multiplication of the physical channel
requirement with the corresponding service activity factor i.e.
int_chs ph _ chs activity
18

Evaluation of the fractional loads for UL & DL. The UL fractional load for a
service class is given by:
m
fL _ UL
1 i _ UL PowerRiseUL
W
1
1. Traffic per Cell
Eb / N 0 _ BTS MDCgain _ UL
Erlang or kbit/s
R 10
10
Where:
2. Traffic Channels
m is the number of interfering channels

Eb/No is the target energy per bit to interference spectral
density ratio
W is the chip rate
R is the bit rate

MDCgain_UL is the macro diversity gain on the UL due to soft
handover
PowerRiseUL is the average increase in transmit power due to
power control.
5. Fractional Load
i_UL is the ratio of other to own cell interference.
The total UL load is obtained by summing the UL fractional loads over all
service classes.
19

DL fractional load for a service class is given by:
1. Traffic per Cell

Erlang or kbit/s
fL _ DL
m 10
Eb / N 0 _ MS MDCgain _ DL
10
1 Orth _ DL i _ DL
where,
2. Traffic Channels
m is the number of interfering channels

Eb/No is the target energy per bit to interference spectral
density ratio
W is the chip rate

R is the bit rate

MDCgain_DL is the macro diversity gain on the DL due to
soft handover
Orth_DL is the downlink orthogonality
5. Fractional Load
i_DL is the ratio of other to own cell interference.
The total downlink load is obtained by summing the downlink fractional loads
over all service classes.
20
Total base station DL power R99 traffic

Total DL base station transmit power can be a limiting factor in highly
loaded cell
TOT
PDL
N E
1
b N0 j
PN
j LSERV , j
1 DL
W Rj
j 1
PCCCH
1 DL
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
21
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 fractional 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 Load

12.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%
22
HSDPA throughput
Available HSDPA power can be calculated from the total power
equation when DCH traffic load and maximum allowed DL power is
known
TOT
DL
23
MAX
DL
N E
1
b N0 j
PN
j LSERV , j
1 DL
W Rj
j 1
PCCCH
PHSDPA
1 DL 1 DL
HSDPA Cell Throughput

The total cell
throughput of 1320
kbps
Without any HSDPA
traffic, the Rel99 DCH
cell capacity equals
780 kbps
Using 7-8 W for HSDPA,
the total cell
throughput is
increased by a factor
1320/780=1.69
5-code HSDPA
16QAM
1 WSPC/cell
24
HSUPA throughput
The available UL load for HSUPA is calculated when the R99 traffic UL
load is known
Max Load HSUPA = Max Cell Load R99 Traffic Load
Available UL HSUPA load can be converted to HSUPA bit rate by using

the UL load equation and EbNo/Bit rate table used also in power budget
calculation
fL _ UL
1
W
1
R 10
25
EbNO _ HSUPA
10
1 i _ UL PowerRiseUL
HSUPA throughput from available load

Vehicular A 30 km/hr
10 % BLER
Bit Rate
(kbps)
32
64
128
256
384
768
1024
1450
1920
EbNo
(dB)
1.3
0.6
-0.2
-0.6
-0.6
-0.9
-0.9
-0.4
1.1
C/I
(dB)
-19.5
-17.2
-15.0
-12.4
-10.6
-7.9
-6.6
-4.6
-1.9
Load
(%)
2%
3%
5%
9%
13%
23%
29%
42%
65%
5 % BLER
Bit Rate
(kbps)
32
64
128
256
384
768
1024
1450
1920
EbNo
(dB)
1.5
0.4
-0.1
-0.5
-0.6
-0.8
-0.8
-0.3
1.4
C/I
(dB)
-19.3
-17.4
-14.9
-12.3
-10.6
-7.8
-6.5
-4.5
-1.6
Load
(%)
2%
3%
5%
9%
13%
24%
30%
43%
67%
1 % BLER
Bit Rate
(kbps)
32
64
128
256
384
768
1024
1450
1920
EbNo
(dB)
1.8
0.9
0
-0.4
-0.3
-0.7
-0.6
-0.2
1.9
C/I
(dB)
-19.0
-16.9
-14.8
-12.2
-10.3
-7.7
-6.3
-4.4
-1.1
Load
(%)
2%
3%
5%
9%
14%
24%
31%
44%
72%
i _ UL PowerRiseUL 0.65
26
Module Contents
Summary of inputs
27
Channel element Calculation

Note that the channel element means the same as the hardware channel.
Traffic profile per cell
The number of channel elements per BTS are calculated so that first
the needed traffic channels per BTS (not sector by sector as in
fractional load calculations) is calculated.
This is done per BTS since the Code Channels are in one pool over the whole BTS.
Traffic profile per BTS
Traffic
channels per
BTS
Add SHO
overhead for
UL and DL
Convert the number
of physical channels
per service into
channel elements
The traffic per BTS is calculated from the calculated number of

subscribers per BTS and from the subscriber profile.
Then the necessary traffic channels per BTS per service is calculated
by using the same formulas as in previous slides (as well as the
number of physical channels).
Next the soft handover overhead is added to the calculated traffic
channels to get the number of physical channels per BTS.
note that this soft handover overhead addition is done for both UL and DL.
The channel element need for different services is following

Speech (16 kbit/s) => 1 channel element
64 kbit/s service (RT or NRT) => 4 channel elements
28
Channel element Calculation

Add the needed
number of channel
elements for
signalling
Check the
amount of
data
throughput
for the BTS
Common channel processing

Flexi FSPA: 26 channel elements / 1-3 cells
Higher due to optimised traffic channel processing
capability
WSPA: 8- channel elements/cell

WSPC: 16 channel elements / 1-3 cells
Required number of channel elements is

calculated for UL and DL separately Maximum
selected
Channel element includes both UL & DL processing
power
With asymmetric services and HSDPA different
requirements for UL and DL
29
Channel element Calculation HSDPA

5 codes, 16 users, 3.6 Mbit/s 32 channel elements of FSPA or WSPC
10-15 codes, 48 users, max. 10.8 Mbit/s One whole FSPA or WSPC
Possible configurations
One FSPA or WSPC per BTS with 5 codes (1-3 cells) 3.6 Mbit/s per BTS
Resources freely shared between cells
One FSPA or WSPC per cell with 5 codes 3.6 Mbit/s per cell
Code Shared HSDPA Scheduler max. 10.8 Mbit/s per BTS
One whole FSPA (64 CE/80 CE*) or WSPC (64 CE) for 1-3 cell
Max. 48 users freely divided between cells, transmit to max. 3 users
simultaneously
One FSPA or WSPC per cell with 10-15 codes max. 10.8 Mbit/s per cell
Associated channels have to be taken into account for each HSDPA user
DL associated signaling channel = 1 channel element
UL associated signaling + traffic channel = (depends on UL data rate)
* In RAS06 SW level 80 CE/FSPA

30
WSPC capacity for DCH and HSDPA, example

INPUTS:
Suppose the Rel99 traffic requires 30 CE in DL and 20 in UL (SHO OH
included)
The average number of HSDPA users is assumed to be 5 and associated UL
traffic is carried on 64kbps bearer
One WSPC card is allocated for HSDPA
BTS configuration is 1+1+1
RESULT:
DL CEs = 30 +5*1 = 35
UL CEs = 20 +5*4 = 40
Total CEs for traffic + CCHs = 40 +16 =56
HSDPA takes 32 CEs, so totally we need capacity of 56 + 32 = 88 CEs.
For this capacity two WSPC cards is required
31
Channel element Calculation HSUPA

The maximum number of HSUPA connections per Node B is 24 while the
maximum number per cell is 20
Minimum capacity reserved for HSUPA when the feature is activated is 8 CE
More capacity is dynamically reserved when needed and available from other
traffic
Minimum fixed allocation can be reserved Decrease capacity for other traffic
# HSUPA users/BTS
32
CE required for HSUPA

Ultrasite (WSPC)
Flexi
14
32
32
58
48
56
9 12
48
56
13 16
64
80
17 20
64
80
21 24
64
80
This capacity is reserved in

both UL and DL CEs.
Module 9 Dimensioning process

Summary
Dimensioning process involves
Configuration planning Power budget
Capacity and coverage planning Cell range
and load
The output on dimensioning process is initial network
and site configuration
Number of sites/cell
Nominal antenna height
33

Dimensioning Process: Pre-Planning Detailed Planning Post - Planning

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dimensioning Process: Pre-Planning Detailed Planning Post - Planning

Uploaded by

Copyright:

Available Formats

Dimensioning process

Coverage and Capacity

Site selection and planning

Nokia Siemens Networks

Presentation / Author / Date

Nokia Siemens Networks

Presentation / Author / Date

Nokia Siemens Networks

Presentation / Author / Date

Nokia Siemens Networks

Presentation / Author / Date

Dimensioning Process Description

Coverage limited max. cell

Compute cell loading from

Planning threshold definition and Cell range

Cell load and throughput calculation Cell

Compare cell loading with the

Cell range known

Nokia Siemens Networks

Presentation / Author / Date

R99 service link budget for selected service(s)

Base station configuration selection and

Cell load Initial load

DL power Max. power

HSPA throughput Minimum throughput

Cell range&area Number of cells

Dimensioning Process Description

Compare cell loading with the

Nokia Siemens Networks

Presentation / Author / Date

Coverage limited scenario

Complete process is repeated with a lower

The reduction in system loading used in the

Dimensioning Process Description

Compare cell loading with the

Nokia Siemens Networks

Presentation / Author / Date

System loading is greater than the maximum

Maximum DL power is exceeded

HSPA throughput (UL or DL) is lower than

Cell capacity must be increased or the cell

Dedicated HSPA carrier also possible

Reduced cell range

fewer users loading

A reduction in cell range is made and the

The reduction in cell range is done iteratively

Nokia Siemens Networks

Presentation / Author / Date

Input parameters overview

Nokia Siemens Networks

Presentation / Author / Date

Gives an Estimation of the

Capacity Related Input

Asymmetry between UL an DL traffic for NRT Services (Downloading 1/10)

Nokia Siemens Networks

Presentation / Author / Date

Capacity Related Input

Nokia Siemens Networks

Presentation / Author / Date

HSPA related dimensioning inputs

The required HSPA capacity inputs can be given as

Nokia Siemens Networks

Presentation / Author / Date