Diseo y Planificacin De Redes De

Banda Ancha Mvil HSPA Y 4G

AGOSTO 2016
Henry A. Vasquez
Master en Comunicaciones Mviles
Magister en Ingeniera de Telecomunicaciones

Cell Planning and Dimensioning Procedure and

Process

Cell Planning and Dimensioning

Procedure and Process

.
.
.

Coverage Planning and Dimensioning

Steps

The Target of the Link Budget Calculation:

Estimate the maximum allowed path loss on radio
path from transmit antenna to receive antenna
Reach the specific radio conditions i.e.:
minimum Eb/No (and BER/BLER) requirements

location probability settings

Lpmax_UL

Lpmax_DL

Required penetration loss

Calculate maximum cell range R using maximum
allowable path loss (MAPL)
From cell range number of BSs can be calculated

Number of sites depends on network configuration:

LEVEL and QUAL depend on
3 sectors
technology:
6 sectors
- 2G - RXLEVEL and RXQUAL
- 3G - RSCP and ECNO
Omni
- 4G - RSRP and RSRQ
2 sectors

BS

BS

BS
R

For HSDPA/HSUPA for given cell range throughput at

cell edge can be calculated and adjusted

BS

BS

BS

BS

Coverage Planning and Dimensioning

Area related Parameters
Area to under investigation [sqkm]
area where dimensioning is done
Required coverage [%]
percentage of area which has to be under coverage
Clutter type
Dense Urban
Urban
Suburban
Rural
Road
impacts propagation model parameters

Deployment class
Basic
Mature
High end
User Specific
Penetration loss [dB]
Standard deviation [dB]
Area/edge location probability [%]

Coverage Planning and Dimensioning

Area related Parameters

Site layout

Coverage Planning and Dimensioning

Transmitting End BTS Side (DL)
Site configuration
Feeder solution with TMA
Feeder solution without TMA
Feederless
Fiber Optical solution (next slide)
Antenna height [m]
RF Power
8,15,20,30,40,60 [W]

Feeder parameters
attenuation [dB/100m]
Default:
2 [dB] for feeder solution
0.5 [dB] for feederless solution
Fiber Optical (<0.5 [db]
TMA (MHA) usage
Feeder loss reduction for UL
lower Noise Figure
0.5 [dB] as TMA insertion loss
Antenna Gain [dBi]
depends on
site configuration
frequency
vendor

Antenna System Interconection

Elements

Coverage Planning and Dimensioning

Transmitting End BTS Side (DL)
Rel99 specific
DL DCH Calculation
Users at cell edge
Users inside cell

(recommended)

HSDPA specific
HSDPA Power per User per TTI [%]
Max power per user
Default: 40%
Rel99 Power per Cell [%]
If Rel99 users are in the cell
Other HSDPA Power per TTI [%]
HS-SCCH and ass. DCH Power [%]

Signaling ratio [%]

Default ~20%

Coverage Planning and Dimensioning

Transmitting End UE Side (UL)
Antenna Gain
Default: 0 [dB]

Tx Power
Depends on service used
Class 4 21 [dBm] (for voice)
Class 3 24 [dBm] (for data)

Body loss
Depends on service used
Voice: 3 [dB]
Data: 0 [dB]

UE Category
E-DCH Cat.1 5
Impacts supported features

Coverage Planning and Dimensioning

Propagation related Parameters

Frequency Band
UMTS 2000
UMTS/LTE 1900
UMTS/LTE 1700/2000
UMTS 1500
UMTS 900
UMTS 850
Channel Model
Vehicular A 3 km/h
Vehicular A 30 km/h
Vehicular A 50 km/h
Vehicular A 120 km/h
Propagation model
One Slope
Two Slope
Davidson-Hata
COST 231
User defined

Coverage Planning and Dimensioning

Propagation related Parameters
Fading [dB]
Depending on
propagation model
Frequency
Clutter type
Fast fading
Fast Fading Margin [dB]
Slow fading (Shadowing)
Shadowing Margin [dB]
Depends on clutter parameters
Gain Against Shadowing [dB]

Coverage Planning and Dimensioning

Receiving End
BTS Side (UL)
Noise Figure

Frequency dependent
Default:
2 [dB] for Flexi
3 [dB] for UltraSite

Interference Margin [dB]

Cell Load [%]

Own Connection Interference [dB]

UE Side (DL)
Noise Figure

Default: 7 [dB]
Interference Margin [dB]
Cell Load [%]

Only for Rel99

UE Category

Coverage Planning and Dimensioning

Technology dependent Parameters
Technology (DL / UL)
Rel99 / Rel99
HSDPA / Rel99
HSDPA / HSUPA

Release
Original 3GPP features
New Features from vendors

Bearer type
Rel99 / Rel99
CS (e.g. AMR, CS 64)

PS (e.g. PS 64/64, PS 384/128)

HSDPA / Rel99
HSDPA / HSUPA

Coverage Planning and Dimensioning

Technology dependent Parameters

Coverage Planning and Dimensioning

Technology dependent Parameters
Bearer type

Coverage Planning and Dimensioning

Technology dependent Parameters

Bearer type

HSxPA Bearer

R99 Bearer

Coverage Planning and Dimensioning

Coverage Planning and Dimensioning

Data Rate [kbps]
Specific for each Bearer

Information rate [dB/Hz]

Calculated on Data Rate

Required Eb/No [dB]

Depends on:
Service
Channel model
Frequency

Coverage Planning and Dimensioning

CPICH RSCP: Received Signal Code Power, the received power on one code measured on the Primary
CPICH. The reference point for the RSCP shall be the antenna connector of the UE.

CPICH Ec/No : The received energy per chip divided by the power density in the band. If receiver diversity is not in use by the
UE, the CPICH Ec/No is identical to CPICH RSCP/UTRA Carrier RSSI. Measurement shall be performed on the Primary CPICH.

Coverage Dimensioning
Link Budget Formula (DL,UL)
Pet

PIRE
PRA
(4)

TX
(1)

Ltt

Pdr

Pr

Pt

Pt

Circuito
T
de
Acoplo
(2)

Pr

Circuito
AT
de
Antena
(3)

IT IR
(5) (6)

Gt

Lat
Gt

(7)

Lb

Lt
Ls
Lg

Circuito
AR
de
Antena
(8)

Gr

Lar

Gr

Circuito
R
de
Acoplo
(9)

Ltr

RX
(10)

Carrier Types
Calculation of required Number of Carriers
Used HSDPA Capacity is proportional to the power used by HSDPA channels
When whole Tx power is available for HSDPA 100% capacity (Max HSDPA Capacity)
When Tx power is shared among Rel99 and HSDPA Max DL capacity of shared HSxPA/Rel99 carriers <100%, depending on Rel99 to HSDPA
power ratio

100% of NodeB Tx Power that can

be used for:

Total Node B Tx Power

Power reservation
for all control
channels per cell
HSDPA, then it refers to 100% of capacity
or
Rel99, then it refers to e.g. 50% of load
or
Rel99 and HSDPA, power is shared
What is the required number of
Rel99 / HSxPA shared carriers?

Carrier Types
Calculation of required Number of Carriers

Number of Rel99 / HSxPA carriers is estimated in the following steps:

1. Calculation of No of carriers with respect to Rel99 and HSUPA load
(UL and DL traffic of Rel99 services + UL traffic of HSDPA services: Rel99 plus HSUPA)

AssignedRe l99_HSUPAL oadUL AssignedRe l99LoadDL

NoCarriers _Rel99_HSU PA roundup max
;
MaxCarrier
Capacity_U
L
MaxCarrier
Capacity_D
L

2. Calculation of DL Rel99 load destined to 1 shared carrier (only Rel99 services)

Rel99LoadP erCarrier_ DL

Rel99loadD L
NoCarriers _Rel99_HSU PA

Now we know how much Rel99 DL

load is allocated to one shared carrier

3. Calculation of usage of available NodeB capacity by DL Rel99 traffic per shared carrier
NBCapacity Usage_Rel9 9

Rel99LoadP erCarrier_ DL
AvailableN BPower
Max DL Rel99 Capacity

Transition from Rel99 load to NodeB Capacity used by Rel99 traffic

Furthermore we know now how much

NodeB Capacity is used for Rel99 traffic

Carrier Types
Calculation of required Number of Carriers
4. Calculation of HSDPA load (DL) per shared carrier

HSDPALoadP erCarrier_ DL

HSDPA Load DL
NoCarriers _Rel99_HSU PA

Now we know how much HSDPA DL

load is allocated to one shared carrier

5. Calculation of usage of available NodeB capacity by HSDPA traffic

Furthermore we know now how much
NodeB Capacity is required for HSDPA
traffic

NBCapacity Usage_HSDP A

HSDPALoadP erCarrier_ DL
AvailableN BPower
Max HSDPA Capacity

6. Check if available NodeB capacity is enough to serve HSDPA plus Rel'99 on one shared
carrier; if not an additional carrier is added
If ReqNBCapacity AvailableN BCapacity then
ReqNoShare dCarriers NoCarriers _Rel99_HSU PA
Else
ReqNoShare dCarriers NoCarriers _Rel99_HSU PA 1
where :
ReqNBCapacity NBCapacity Usage_Rel9 9 NBCapacity Usage_HSDP A

Carrier Types
Calculation of required Number of Carriers Example and resume
Limitations
Max UL Rel99 and HSUPA capacity
Max DL Rel99 capacity

Max HSDPA capacity

Available NB capacity

60%
60%

100%
100%
UL, HSUPA+Rel99 DL, Rel99

1.

80% 19% 24%

NoCarriers _Rel99_HSU PA roundup max
;
roundup (1.65) 2
60
%
60
%

24%
2. Rel99LoadP erCarrier_ DL
12%
2

12%
100% 20%
3. NBCapacity Usage_Rel9 9
60%
85%
HSDPALoadP erCarrier_ DL
42.5%
4.
2
42.5%
NBCapacity Usage_HSDP A
100% 42.5%
5.
100%

ReqNBCapacity 20% 42.5% 62.5%

6.

Assumptions: Load that supposed to be served

on shared carriers
Rel99 load UL
19%
Rel99 load DL
24%
HSPA load UL (Rel99 +HSUPA)
80%
HSPA load DL (HSDPA)
85%

per shared carrier

per shared carrier

Power reservation for

all control channels
per cell

100% of
NodeB Tx
Power

DL HSDPA
traffic
DL Rel99 traffic

ReqNB
Capacity

Coverage Planning and Dimensioning

Soft handover gain [dB]
Rel99:

DL 2.5 [dB]
UL 1.5 [dB]
Soft HO

HSDPA:
0 [dB]
HSUPA:
1.5 [dB]

Softer HO

Coverage Planning and Dimensioning

Link Budget Formula (CPICH)

2ndCarrier and main Ideas for

reselection strategy:
Different strategy for UE in idle mode and UE in RRC connected mode
(cell_FACH, cell_PCH)
UE in idle mode prefer F1
UE in RRC connected mode (cell_FACH, cell_PCH) prefer F2

Coverage Planning and Dimensioning

2ndCarrier and main Ideas for reselection strategy:
CS voice prefer F1
As a requirement and with our idle mode parameter, UE in idle mode is forced to camp on F1, thus, the voice call
should also likely to be made in F1
What if UE making voice call in F2?
Service based HO will handover voice UE to F1
What if F1 is congested?
Load based HO will allow voice UE to HO from F1 to F2 in case of congestion in F1
What if the quality is bad?

Urgency handover will always enable in both frequency to allow the voice UE to HO to different frequency in case
of poor quality/coverage
HSDPA Data prefer F2
Requirement put HSDPA data in F2, but usually UE in idle mode is forced to camp on F1 due to our idle mode
parameter, thus, the beginning of data call always start the data transfer in F1 (The features to redirect to call to F2 at
the setup phase are not available to use here). But after that, we use the feature to handover the data call to F2.
If the UE is HSDPA capable, HSPA capability HO feature will HO those UE to the F2 (co-sector only)
What this feature do with non-HSDPA capable UE?
Do nothing
If the HSDPA capable UE but using R99 NRT DCH bearer in F1 at the moment, will it be transfer to F2?

Yes, by periodic trigger.

When the data call in F2 allow to handover to F1?
Urgency handover will always enable in both frequency to allow the UE to HO to different frequency in case of poor
quality/coverage

Carrier Types
Case 1: Traffic Assignment among Carrier Types
Rel99 only carrier + Rel99/HSPA shared carrier

Rel99 traffic

Rel99 / HSPA
shared carriers

Rel99 traffic
= Max Rel99
carriers
capacity

Rel99 only
carriers

Max Capacity
of Rel99 only
carriers

HSPA traffic

Left Rel99
traffic
All HSPA
traffic

Max Capacity of
Rel99/HSPA
shared carriers

Max Capacity of Rel99 only carriers =

= Max Capacity of Rel99 only carrier * No of possible Rel99 only carriers
Max Capacity of Rel99/HSPA shared carriers =
= Max Capacity of Rel99/HSPA shared carrier * No of possible Rel99/HSPA shared carriers

If max possible carriers capacity is exceeded additional carriers are proposed

Carrier Types
Case 2: Traffic Assignment among Carrier Types

Rel99 only carrier + HSPA only carrier

HSPA traffic

All Rel99
traffic

Rel99 only
carriers

Max Capacity
of Rel99 only
carriers

HSPA only
carriers

Rel99 traffic

All HSPA
traffic

Max Capacity
of HSPA only
carriers

Max Capacity of Rel99 only carriers =

= Max Capacity of Rel99 only carrier * No of possible Rel99 only carriers
Max Capacity of HSPA only carriers =
= Max Capacity of HSPA only carrier * No of possible HSPA only carriers

If max possible carriers capacity is exceeded additional carriers are proposed

1.

Example1:

Inactivity HSCAHO from

F1 to F2

UE in idle mode measure F1 at -10 dB

2.

User make some browsing data (HSDPA)

(pause time < 30 mins)

3.

1 min after stop browsing (PDP still

active as well RRC connection), user
make CS call

4.

1 min after that user started browse

data again

5.

Doing nothing for 1 hour

UE in F1 at Idle

Data/Voice
in F1

Non-dedicated resource in F1

Data/Voice
in F2

Non-dedicated resource in F2

UE in RRC
connected state,
reselect from F1 to
F2

HSDPA

4
2 (cont,)

HS
DP
A

HS
DP
A

Voice

UE in idle mode
reselect from F2 to
F1
3
Cell_PCH -> IDLE

HSD
PA

HSDPA

Service based HO from F2 to F1

HSDPA

HSDPA

HSD
PA

~ 30 mins

Example2:
1.

UE in idle mode measure F1

at -10 dB

2.

User make 1 FTP and when

the FTP end user also deactivate the PDP context

3.

Wait for 1 min

4.

User make 1 FTP again and

when the FTP end user also
de-activate the PDP context

PDP deactivate and go

to idle

UE in F1 at Idle
HSDPA

PDP deactivate and go

to idle
HSDPA

3 (cont,)

Data/Voice
in F1

Non-dedicated resource in F1

Data/Voice
in F2

Non-dedicated resource in F2

So, the data transfer always in F1 in this case.

So do not be surprised if our current script gave
only results in F1

Coverage Planning and Dimensioning

Scrambling Code Planning

Coverage Planning and Dimensioning

Scrambling Code Planning
Two neighbors are identified using the same scrambling code

The applications marks these events as a warning no action

taken for the user(costumer)

Scrambling Code
123

39

Scrambling Code
123

Scrambling Code
Conflict

Coverage Planning and Dimensioning

Scrambling Code Planning
Objective : Detect possible co-SC in

the network
Propose the better SC for a cell, according their neighbors and nearer cells in its work
radius. In SCO Planning we can detected 3 kind of PSC collision:

1. A CO-SC with a direct neighbor, it causes confusion to the mobile and generates drop.
Cell X(123) Y(123)
2. It is not possible add a near neighbor due to that the actual list has a same SC from
another neighbor.
CellX(123)CellY(45) / CellZ(123) : Y can not add Z as neighbor due to X has the
same SC.
3. It is not possible add an indirect neighbor when the mobile has 2 o more radiolinks
connected, due to the compound neighbor list contains a neighbor with the same SC.
CellX(32)CellY(4) CellZ(234) CellW(32)
If a mobiles is connected with Y & Z it could not be possible a relation with W or X in a
softhandover due to this cells have the same SC.

Coverage Planning and Dimensioning

Scrambling Code Planning
Two neighbors are identified using the same scrambling code

The applications marks these events as a warning no action

taken for the user(costumer)

Scrambling Code
123

41

Scrambling Code
123

Scrambling Code
Conflict

Coverage Planning and Dimensioning

Scrambling Code Planning - Second Order SC Example
Based on Scrambling code that are in the neighbors list

The applications marks these events no action taken

Report Missing
neighbor with SC
191

Second Order SC
rejection

SC 191
Cell X SC 30

Cell Z SC 30
SC 30
Neighbors

Unified List

List
SC 30

Neighbors

List
Cell X SC 30
Cell Z SC 30

SC 30

- 64 QAM modulation
- MIMO
- Dual carrier`

CS Voice over HSPA

1Tx 1Rx antenna scheme

Capacity gain UL/DL:

HW: new UE CSoHSPA capable

No HW changes in RAN or Core
feature)

40% 60%

(RAN SW

Enabled with QoS scheduler

Baseline: site 1/1/1, 1Tx-1Rx, PA: 20W, CS voice service Rel99

CS voice call from legacy UE use AMR

bearer, CSoHSPA UE may use HSPA or
AMR on Uu interface

Both are carried by CS core part

Can not be enabled together with MIMO
or DC HSDPA
CSoHSPA capable UE

legacy UE

MIMO (2Tx, 2Rx) 3GPP Release 7

2Tx 2Rx antenna scheme (DL)
HW: 2nd PA per cell 1) , 2nd Tx antenna 2)
categories 3) (Cat. 15-20)

new UE

Supported on 1/1/1, 2/2/2, 3/3/3 sites 4)

Capacity gain DL:

20% 40%

UE throughput gain:

60% 100%

Coverage increase DL [dB]: 2 3

Baseline: site 1/1/1, 1Tx-1Rx DL, PA: 20W, HSPA
- already available on macro sites - 2RxDiv (usually X-pol antennas in
urban/sub-urban)

Maximum one MIMO carrier

1 x 5 MHz

1 x 5 MHz
f1
Uplink

f1
Downlink
Ant1
PA1
cell1

Ant2
PA2
cell 1

- at least 20% of MIMO UE share in MIMO configured cell required

to compensate for capacity loss caused by 2nd PA

Capacity factor

MIMO UE share (network wide)

non-MIMO UE

MIMO UE

Dual Stream only in good CQI areas

Example: fully loaded hexagonal network, cell range=800m, PA=20W, FTP full

Dual-Cell HSDPA 3GPP Release 8

1Tx 1Rx antenna scheme
HW: new UE categories (Cat. 21-24)
Needs 2 carriers (HSPA enabled) on same sector

Capacity gain DL:

15% 25%

UE throughput gain:

80% 100%

Coverage increase DL [dB]: 3.5 4.5

2 x 5 MHz
f1

1 x 5 MHz

f2

Baseline: site 2/2/2, 1Tx-1Rx DL, PA: 20W, HSPA Rel6

f1
Uplink

Downlink

Ant1
PA1
cell1

Ant2
PA1
cell 2

Supported on 2/2/2, 3/3/3, 4/4/4 sites

(shared joint scheduler for 2 cells on
same sector, max 2 DC schedulers per
sector)

DC capacity gain
when # UE (active)
DC UE may gain (throughput ) in any
cell location if scheduled on both carriers

DC capacity gain
Rel5/6/...
(non-DC)

f2
f1

DC capable
UE

Dual Stream (Cell) in any location if UE have enough data in buffer and is
scheduled on both carriers

in shared
Rel99/HSPA scenarios if Rel99 UEs
distributed on both carriers (f1 and f2
shared for Rel99 and HSPA)

Six Sector Site Layout Solution

Sectorization 6 Sectors: Summary
Capacity gain DL:

~80%

Capacity gain DL:

70 80%

Coverage increase DL [dB]: ~2

Baseline: site 1/1/1, 1Tx-1Rx DL, 1Tx-2Rx UL, PA: 20W

Similar site capacity boost as additional

carrier
Especially useful in bandwidth limited
networks (no new carriers)
May be implemented on single site or on
clusters
Antennas to be exchanged by narrow beam
<= 45deg 1)
Additional RF HW for new sectors (may not
be needed if HW Rel2 already on site)
1)

Typical 3 sector, 1 pole installation

with X-pol antennas

The 3 dual bandwidth antennas and often no site

reconstruction if NSN High Performance Site
Solution used (picture on the left)

LTE Capacity Dimensioning Principle

Current Dimensioning based on MCS Distribution

Cell Throughput is calculated on basis of area covered by each

available MCS

Alternative possibility is to replace the calculated results by

simulation results/estimations or by throughput-SINR
curves.

Radio Channel Access Codes

The radio channel
SISO

MISO

Transmit antennas

Receive antennas
SIMO

MIMO

LTE Antenna Techniques

Single User, Multiple User, and Cooperative MIMO

The radio channel

Transmit antennas

Receive antennas

Data Rate Calculation

1.Maximum channel data rate
The maximum channel data rate is calculated taking into account the total number of the available resource blocks in 1 TTI
= 1ms

Max Data Rate = Number of Resource Blocks x 12 subcarriersx (14 symbols/ 1ms)
= Number of Resouce Blocks x (168 symbols/1ms)

2. Impact of the Channel Bandwith: 5, 10, 20 MHz

For BW = 5MHz -> there are 25 Resource Blocks
-> Max DataRate = 25 x (168 symbols/1ms) = 4,2 * Msymbols/s
BW = 10MHz -> 50 ResourceBlocks -> Max DataRate = 8,2 Msymbols/s
BW = 20MHz -> 100 ResourceBlocks -> Max DataRate =16,4 Msymbols/s

Data Rate Calculation

3. Impact of the Modulation: QPSK, 16QAM, 64QAM
For: QPSK 2bits/symbol; 16QAM 4bits/symbol and 64QAM 6 bits/symbol

QPSK: Max DataRate = 16,4 Msymbols/s * 2bits/symbol= 32,8 Mbits/s (bandwith of 20 MHz)
16QAM: Max DataRate = 16,4 Msymbols/s * 4 bits/symbols= 65,6 Mbits/s
64QAM: Max DataRate = 16,4 Msymbols/s * 6 bits/symbols= 98,4 Mbits/s

Data Rate Calculation

4. Impact of the Channel Coding

The effective coding rate is dependent on the Modulation and Coding Scheme selected by the
scheduler in the eNodeB. In practice several coding rates can be obtained. Here it is considered
1/2 and 3/4:
1/2 coding rate: Max Datarate = 98,4 Mbits/s * 0,5 = 49,2 Mbits/s
3/4 coding rate: Max Datarate = 98,4 Mbits/s * 0,75 = 73,8 Mbits/s
5. Impact of MIMO = Multiple Input Multiple Output

If spatial diversity it is used (2x2 MIMO) then the data rate will be doubled since the data is sent in parallel in 2 different
streams using 2 different antennas 2x2 MIMO:
Max Data Rate = 73,8 Mbit/s * 2 = 147,6 Mbits/s