LTE Planning Principles

LTE planning principles
Hans - Jörg Hamers

TSO Access Design
1 LTE planning principles Vodafone confidential

25 August 2014
Understand
Coverage - the key requirements in planning LTE coverage
Understand
Quality / SINR - the key requirements in planning LTE coverage
Understand
RLC Throughput - the key requirements in planning LTE throughput
Neighbours Understand the requirements for planning

- neighbour s
Tracking Areas - tracking areas
Physical Cell ID - physical cell id
Root Sequence ID - root sequence id
LTE in Have an example of

VF-Germany - LTE planning criteria in VF-Germany

25 August 2014
Coverage
Coverage Understand
- the key requirements in planning LTE coverage

25 August 2014
Coverage
Coverage
VF-Target: LTE 800

RSRP: >= -114 dBm
Area: 95 %
Cell Edge: 85 %
(SINR Cell Edge: >= -3 dB)
refers to RS power = 18,2dBm
86% @ -114dBm

25 August 2014
Coverage
Coverage
Challenge: Design target co-located to GSM / UMTS

usage of dual-band antennas
LTE antennas have smaller horizontal beam-width
(105° or 90° 65°)
~ azimuth optimisation required
65°
slightly reduced coverage for 65°
105°

25 August 2014
Coverage
LTE planning principles - Coverage
Comparing: RXLEV in GSM, RSCP in UMTS and RSRP in LTE
Power per Antenna: 20W 43dBm Power per TX carrier: 10W 40dBm
UMTS /WCDMA LTE GSM

43dBm
CPICH power: RS-TX power BCCH-TX power
33/35dBm / 5MHz 18/15dBm / 15kHz & 40dBm /200kHz bandwidth

18dB difference
10MHz bandwidth
GSM and LTE
UMTS and LTE similar path loss
similar path loss
RSCP RSRP RXLEV
UMTS ~ 15 18 20dB difference LTE ~ 22dB difference GSM

Threshold Threshold Threshold
e.g. -114dBm e.g. – 92 dBm

e.g. - 99dBm
Coverage is similar!
LTE planning principles Vodafone confidential
25 August 2014
Coverage
Coverage
Comparing: 3G – LTE coverage

3G-RSCP (2.1GHz) LTE-RSRP (2.6GHz)
Threshold adaptation required: 3G (whole bandwidth) --- LTE (subcarrier)

25 August 2014
LTE planning principles Quality / SINR
Quality / SINR Understand

- the key requirements in planning LTE coverage

25 August 2014
Quality / SINR
VF-Target: LTE 800

SINR: >= -3 dB
Area: 95 %
Cell Edge: 85 %
(RSRP Cell Edge: >= -114 dBm)
refers to RS-SINR
83% @ -3dB

25 August 2014
Quality / SINR
Challenge: Rollout target co-located to GSM / UMTS

usage of dual-band antennas
LTE antennas have smaller horizontal beam-width
(105° or 90° 65°)
~ separated tilt settings required,

at least optimisation
65°
reduced overlapping
increased quality
for 65°
105°

25 August 2014
Quality / SINR
Conclusion:
Change of antenna pattern from 105° or 90° to 65° leads to
reduced coverage in inter sector direction (+/-60°)
higher coverage in main direction
in clustered scenarios advantages and disadvantages nearly compensate

~ 5% reduction of coverage expected
might be compensated by larger antenna (gains +1,5dB) and optimisation
but
reduced overlapping => reduced interference

higher capacity and data rates:
105° to 65°: +50% capacity
90° to 65°: +25% capacity

25 August 2014
LTE planning principles RLC
Throughput
Understand
RLC Throughput
- the key requirements in planning RLC throughput

25 August 2014
RLC Throughput Throughput
VF-Target: LTE 800

RLC >= 1 Mbit/s (Cell edge)
5.2 Mbit/s
@ 50%

25 August 2014
RLC Throughput Throughput
Challenge: prediction depends on SINR and vendor adaptation into Atoll
Bearers Bearer Selection

Huawei / Ericsson Adaptation! Index
1
Name Modulation Channel Coding Rate Bearer Efficiency
QPSK 1 QPSK 0.11 0.23 Thresholds
2 QPSK 2 QPSK 0.15 0.3
3 QPSK 3 QPSK 0.18 0.37 Best Bearer SINR
4 QPSK 4 QPSK 0.24 0.49 1 ‐8
5 QPSK 5 QPSK 0.3 0.59 2 ‐7
Global Parameters 6
7
QPSK 6
QPSK 7
QPSK
QPSK
0.36
0.44
0.73
0.88
3 ‐6
4 ‐4.82
Cyclic Prefix [us] 4.69 8 QPSK 8 QPSK 0.51 1.01
9 QPSK 9 QPSK 0.6 1.19
5 ‐3.64
Overhead PDCCH [Syms] 3 6 ‐2.62
10 16QAM 1 16QAM 0.34 1.34
Overhead PUCCH [RB] 2 11 16QAM 2 16QAM 0.37 1.49 7 ‐1.48
Uplink power control margin [dB] 1 12 16QAM 3 16QAM 0.42 1.68 8 ‐0.45
13 16QAM 4 16QAM 0.47 1.88 9 0.63
14 16QAM 5 16QAM 0.54 2.15 10 1.82
Transmitter 15
16
16QAM 6
64QAM 1
16QAM
64QAM
0.6
0.43
2.38
2.58
11 2.72
17 64QAM 2 64QAM 0.45 2.68 12 3.94
Noise Figure (dB) 2.3 18 64QAM 3 64QAM 0.5 2.98 13 4.92
19 64QAM 4 64QAM 0.55 3.28 14 5.61
20 64QAM 5 64QAM 0.59 3.53 15 6.48
21 64QAM 6 64QAM 0.64 3.83 16 7.41
Cell 22 64QAM 7 64QAM 0.69 4.13 17 8.5
23 64QAM 8 64QAM 0.74 4.43
18 9.43
Max UL Noise Rise (dB) 3 24 64QAM 9 64QAM 0.8 4.78
25 64QAM 10 64QAM 0.86 5.17 19 10.23
Traffic Load (DL) (%) 40
26 64QAM 11 64QAM 0.89 5.37 20 11.2
Traffic Load (UL) (%) 40 27 64QAM 12 64QAM 0.93 5.57 21 12.16
22 13.1
23 13.94
24 14.97
25 15.96
14 LTE planning principles Vodafone confidential 26 16.94
27 18.21
25 August 2014
LTE 1800 on GSM 1800 Grid
Strategy: One to one:
Average site distance:
1568 m outer ring

all
521 m inner ring
provided sites
226 m city center
RSRP Indoor
☺ good coverage
but
RS-SINR
poor SINR
Throughput +
throughput

25 August 2014
RSRP Indoor
(refers to RS power = 18,2dBm)
☺
RSRP [dBm]
100
90
80 99,3% @ >=-110dBm)
70
covered area [%]
60
50
40
30
20
10
0
‐130 ‐120 ‐110 ‐100 ‐90 ‐80 ‐70 ‐60 ‐50 ‐40 ‐30

25 August 2014
RS-SINR
RS SINR [dB]
100
90
80 79,5% @ >=-3dB
70
covered area [%]
60
50
40
30
20
10
0
‐20 ‐15 ‐10 ‐5 0 5 10 15 20 25 30

25 August 2014
Throughput
50% @ 3.7 Mbit/s

25 August 2014
LTE 800 as “Like for like” on GSM 900 Grid Customer Experience
Design Target
Peak PDSCH throughput by number of measured neighbours (10dB window)
19
Optimise overlapping within network with target: 1st to 2nd server outside 10dB

window
25 August 2014
LTE 800 as “Like for like” on GSM 900 Grid
Capesso settings:
Overlapping target
1st – 4th Server
Globally: 10 dB
Weight: 5
Traffic weight applied

25 August 2014
RSRP Indoor - Initial
100,00
LTE 800 indoor coverage

90,00
80,00
- RSRP >= - 108 dBm 70,00
Initial
60,00
93,3% @ -
Area [%]
50,00
40,00
108dBm
30,00
20,00
10,00
0,00
30
4
26
22
18
14
10
06
02
0
-9
-9
-9
-8
-8
-7
-7
-7
-6
-6
-5
-5
-1
-1
-1
-1
-1
-1
-1
-1
25 August 2014
Overlapping Area - Initial
LTE 800 overlapping 30
- Server within 10 dB window INI

25
20
Area [%]
15
10
0
>= 6 5 4 3 2 1

25 August 2014
LTE 800 overlapping

- Overlapping areas can be reduced in 6, 5 and 4 server areas
- Increase of areas with 1, 2 and 3 server
- Not much difference between E, EM and EMA optimisation
Overlapping Area
35
INI
30 E
EM
EMA
25
20
Area [%]
15
10
0
>= 6 5 4 3 2 1
Recommendation: Implement only electrical tilt changes

to achieve highest gain with lowest costs
25 August 2014
LTE 800 captured traffic

- Reduction of Overlapping areas >= 4 server in high traffic areas
Overlapping Areas and Captured Traffic [%]

40,00
35,00
Initial
30,00
Optimised
25,00
Traffic [%]
20,00
15,00
10,00
5,00
0,00
>=6 5 4 3 2 1
Number of Servers

25 August 2014
Neighbours
Tracking Areas
PCI
Neighbours Understand the requirements for planning

Tracking Areas
- neighbours
Physical Cell ID
Root Sequence id - tracking areas
- physical cell id
- root sequence index

25 August 2014
Neighbours, Tracking Areas, PCI Neighbours
Tracking Areas
PCI
Two possible neighbour strategies:
usage of
Atoll
• prediction based automatic allocation

(no major difference to UMTS)
• used as initial definition
Automatic Neighbour Relation (ANR)
• UE performs network measurements

• neighbour relations defined based on measurements
• also used for initial definition

• used to maintain and optimise neighbours defined by Atoll

25 August 2014
Tracking Areas
PCI
LTE / SAE Mobility Areas
two areas are defined for handling of mobility in LTE /SAE
The cell
• identified by the Cell ID
Tracking Area (TA)

• it is the successor of location and routing area from 2G/3G
• when a UE is attached to the network, the MME will know the UE’s
position on tracking area level
• in case the UE has to be paged, this will be done in the full tracking area
• Tracking areas are identified by a Tracking Area Identity (TAI)
TAI = MCC + MNC + TAC with

TAI = Tracking Area Identifier
Range for TAC: 1 – 65.535 MCC = Mobile Country Code (Germany = 262)
LAC and TAC share the same ranges of values MNC = Mobile Network Code (VF-DE = 02)

25 August 2014
Tracking Areas
PCI
Concept of TA lists
the MME provides the UE with a list of tracking areas where the UE registration is valid
when paging a UE, the MME sends a paging message to all eNodeBs in the TA list
the MME sends the TA list to the UE during the update procedure
TA updates occur periodically and when a UE enters a cell with a TAC not in the current TA list
TA list enables avoiding frequent TA updates due to ping pong effects along the TA border
this is achieved by including the old TA in the new TA list received by TA update
25 August 2014
Tracking Areas
PCI
“Multi Tracking Area Registration “ Concept
UE only triggers TAU when moving

to a cell belonging to a cell TA3 TA5
belonging to a TA not in eNB eNB
TA list for that UE.

TA1
eNB eNB eNB
UE = TA1, TA2, TA3
eNB eNB eNB
eNB 2 eNB eNB eNB
eNB eNB eNB UE = TA5
eNB eNB 1 eNB 3
eNB eNB
TA2
UE = TA2, TA3, TA4
eNB TAU procedure is triggered
TA4
may minimize the numbers of Tracking area updates

25 August 2014
Neighbours, Tracking Areas, PCI
Neighbours
Tracking Area Planning Rules Tracking Areas
PCI
Planning of TA means to balance TA-update load and
paging load. TA border
Considerations related to user mobility:
- Borders between TAs need to intersect major traffic
flows perpendicular
- Intersections of traffic flows are to be kept as far
away as possible from TA borders (low traffic area)
Sources of traffic flow:
- Highways/Motorways – crossing TA borders
- Railroad tracks, especially for high speed trains
Considerations related to RF conditions:
- Avoid TA borders in areas with undefined coverage
- e.g. along a river covered from multiple sectors
- e.g. in a valley
Considerations related to paging load
- If not already considered by RF planning,
consider balanced user presence across tracking areas
- Tracking Areas in dense urban areas will be geographically
smaller compared to rural areas, however, the eNodeB
count per area might remain comparable
Considerations related to 4G-3G-2G Interworking
- LTE MME combined with SGSN. Aggregated tracking
areas covered by combined core nodes should be
consistent for GSM, UMTS and LTE areas.
- This will improve the execution time of interworking procedures Consistent TA/RA Planning with
30 between RATs
LTE planning (e.g. in case of a voiceVodafone
principles call with CS fallback scenario).
confidential
combined core nodes
25 August 2014
Tracking Areas
PCI
Neighbours and Cell ID planning criteria (1)
Cell ID is required to identify each cell

a Cell ID is the combination of one of 3 sequences supported by P-SCH and the
group ID supported by S-SCH
so realising a Cell ID planning = realising P-SCH planning and S-SCH planning
the strategy recommended is to use the same S-SCH per site which induces that
each sector uses different P-SCH sequence
For more details on PCI

planning please see
dedicated PCI planning
slides.
NID(1) = 0 …167, NID(2) = 0,1.2; NIDcell = 3NID(1)+ NID(2)

25 August 2014
Tracking Areas
PCI
The main criteria are the following ones:
• considering two cells “Cell A” and “Cell B”, on the same frequency carrier using the
same Cell ID, the distance between those must satisfy
– RSRP criteria
– at “Cell A” edge (RSRP “Cell A” ≤ -115 dBm): RSRP “Cell A” ≥ RSRP “Cell B” + 10dB
– at “Cell B” edge (RSRP “Cell B” ≤ -115 dBm): RSRP “Cell B” ≥≥RSRP “Cell A” + 10dB
• the distance depends on propagation path loss, the environment and the frequency

25 August 2014
Tracking Areas
PCI
Examples of distance criteria:

• Dense urban / urban
– 2,0 km @ 2600 MHz considering 600m cell radius
– 2,5 km @ 1800 MHz and 2100 MHz considering 700m cell radius
– 5,5 km @ 850 MHz and 900 MHz considering 1,7km cell radius
– 6,0 km @ 700 MHz considering 1,9km cell radius
• Suburban
– 6,0 km @ 2600 MHz considering 1,8km cell radius
– 20,0 km @ 700 MHz considering 6km cell radius
• Rural
– 21,0 km @ 1800 MHz and 2100 MHz considering 7km cell radius
– 60,0 km @ 850 MHz and 900 MHz considering 18km cell radius

25 August 2014
LTE Design Standard on Uplink Physical Random Access
Access Channel Root Sequence Index planning
Principle & gain
• PRACH preambles created from Root sequences to
get Access to the eNode B by the UE
• 838 RootSequences are available to generate the
PRACH preambles by combined cyclic shifting
• If same root sequences used in neighbouring cells overlap,
the transmitted preamble may be detected in multiple cells
• The false RACH detection alarm probability may be
increased
• RootSequenceIndex (RSI) points to the first root
sequence to be used when generating the set of 64
preamble sequences
• Number of root sequences allocated to a cell depends
on the cyclic shift Ncs linked to the cell range (table)
• RSI planning prevents blocking of UE Random
Access and drops during Handover
Cell range: 15km 10 Root sequences RSIs:10, 20…
rootSeqIndex=30 Re-use factor: 83 rootSeqIndex=90

{30…39} {90…99}
rootSeqIndex=0
eNB# 2 rootSeqIndex=60 eNB## 4
{0…9}
{60…69}
eNB#1 rootSeqIndex=50rootSeqIndex=40 rootSeqIndex=110 rootSeqIndex=100
eNB # 3 {110…119} {100…109}
{50…59} {40…49}
rootSeqIndex=20 rootSeqIndex=10 rootSeqIndex=80 rootSeqIndex=70
{20…29} {10…19} {80…89} {70…79}
34 Vodafone confidential
Root Sequence (RS) allocation & Root Sequence Index (RSI)
re-use factor
Maximum Number of Total number of Rootsequences(838)
RSI Re-use
Cell range Root sequences -------------------------------------------------
factor:
per cell Root sequences required per cell
Default Number of 838

Cell range: Root sequences Re-use factor: ----- 83 cells
max. 15km per cell: 10 10
Optimised 838
Number of
Adapted to: Re-use factor: ---------- 83 to 838
Root sequences
Max. Cell range 1 to 10 cells
per cell: 1 to10
(see table)
Rural Number of 838
Cell range: Root sequences Re-use factor: ----- 83/38 cells
15km /30km per cell: 10/22 10/22
Maximum 0,8 1,0 1,5 2 2,6 3,5 4,3 5,5 7,5 10 12 15

cell range in km
RS per cell default 1 2 2 2 2 3 3 4 5 6 8 10
High speed scenario is for further elaboration!
35 Vodafone confidential
LTE in
VF-Germany
LTE in Have an example of

VF-Germany
- LTE planning criteria in VF-Germany

25 August 2014
LTE in VF-Germany
LTE in
VF-Germany
Planning strategy to achieve performance targets:
planning criteria are defined for loaded network scenario
site / cluster design within regions based on planning criteria
headquarter performs KPI validation for loaded network scenario

• no separate KPI validation for initial unloaded network
• assuming in case that KPIs are achieved for loaded network they will also be achieved for unloaded network
• feedback to the regions if KPIs for loaded scenario are not reached
headquarter provides coverage maps for vendor as initial input

for “Performance Acceptance”
• maps are generated for both scenarios
measurement of “Acceptance KPI” is done for unloaded network

25 August 2014
LTE in VF-Germany
LTE in
VF-Germany
Planning targets are defined in that way, that performance targets can be
achieved within the acceptance measurements.
Performance Acceptance Process: Planning Targets:
(Ready for Costumer)
• based on stationary and mobility • coverage target:

measurements – LTE coverage ≥ 95% GSM coverage
for traffic relevant areas
• targets for stationary measurements
measurement 1: SINR > 15dB • performance targets:
– average: 30Mbit/s (DL) / 10Mbit/s (UL) – cell edge: 5Mbit/s (DL) / 2,5Mbit/s (UL)
– 95% percentile: 50Mbit/s (DL) / 20Mbit/s (UL) max. path loss 148dB
SINR = -1dB (100% load)
measurement 2: cell edge, RS-RSRP = -115dBm
– average: 2,5Mbit/s (DL) / 1,2Mbit/s (UL) corresponds to
– 95% percentile: 5Mbit/s (DL) / 2,5Mbit/s (UL) RSRP = -115 dBm
• planning target is defined by measurement 2 – overlapping: <10% (4er)

10dB margin

25 August 2014
LTE in VF-Germany
LTE in
VF-Germany
Coverage Map Planning Targets / Performance Targets
Planning Assumptions:
• performance goals in UL & DL according requirements in RfQ
• Stationary mobile: P_max = 23dBm; G_ant= 0dBi
• G_ant = 16dBi; max_feeder_loss = 1dB
• RS-EIRP: 18dBm + 16dBi – 1dB = 33dBm
• max pathloss: 148dB (without any margin, 50% reliability)

• RSRP = -115dBm (cell edge as minimum outdoor level)
means:
• measurement errors / variations need to be taken into account: 10dB
• measurement route should be planed according to planning value: > -115dBm
• >90% of all measured pixels should be better than -105dBm in the predicted area
• Range -105 … -115dBm takes into account prediction errors: at least 50% of the measurement point
of this predicted area may have measurement levels ≥ -115dBm
• in case of measured RSRP level of -115dBm the
corresponding cell edge performance shall be
measured according to RfQ requirements planning
uncertainty
• levels <-120dBm are expected to be not covered

25 August 2014
25 August 2014

LTE Planning Principles - 9

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

LTE Planning Principles - 9

Hochgeladen von

Copyright:

Verfügbare Formate

Hans - Jörg Hamers

1 LTE planning principles Vodafone confidential

Neighbours Understand the requirements for planning

LTE in Have an example of

2 LTE planning principles Vodafone confidential

- the key requirements in planning LTE coverage

3 LTE planning principles Vodafone confidential

VF-Target: LTE 800

refers to RS power = 18,2dBm

4 LTE planning principles Vodafone confidential

Challenge: Design target co-located to GSM / UMTS

~ azimuth optimisation required

5 LTE planning principles Vodafone confidential

Comparing: RXLEV in GSM, RSCP in UMTS and RSRP in LTE

UMTS /WCDMA LTE GSM

CPICH power: RS-TX power BCCH-TX power

33/35dBm / 5MHz 18/15dBm / 15kHz & 40dBm /200kHz bandwidth

UMTS ~ 15 18 20dB difference LTE ~ 22dB difference GSM

e.g. -114dBm e.g. – 92 dBm

Comparing: 3G – LTE coverage

Threshold adaptation required: 3G (whole bandwidth) --- LTE (subcarrier)

7 LTE planning principles Vodafone confidential

Quality / SINR Understand

8 LTE planning principles Vodafone confidential

VF-Target: LTE 800

9 LTE planning principles Vodafone confidential

Challenge: Rollout target co-located to GSM / UMTS

~ separated tilt settings required,

10 LTE planning principles Vodafone confidential

Change of antenna pattern from 105° or 90° to 65° leads to

reduced coverage in inter sector direction (+/-60°)

higher coverage in main direction

in clustered scenarios advantages and disadvantages nearly compensate

reduced overlapping => reduced interference

11 LTE planning principles Vodafone confidential

12 LTE planning principles Vodafone confidential

VF-Target: LTE 800

13 LTE planning principles Vodafone confidential

Challenge: prediction depends on SINR and vendor adaptation into Atoll

Bearers Bearer Selection

1568 m outer ring

15 LTE planning principles Vodafone confidential

16 LTE planning principles Vodafone confidential

17 LTE planning principles Vodafone confidential

50% @ 3.7 Mbit/s

18 LTE planning principles Vodafone confidential

Optimise overlapping within network with target: 1st to 2nd server outside 10dB

20 LTE planning principles Vodafone confidential

LTE 800 indoor coverage

- Server within 10 dB window INI

22 LTE planning principles Vodafone confidential

LTE 800 overlapping

Recommendation: Implement only electrical tilt changes

LTE 800 captured traffic

Overlapping Areas and Captured Traffic [%]

24 LTE planning principles Vodafone confidential

Neighbours Understand the requirements for planning

- root sequence index

25 LTE planning principles Vodafone confidential

Two possible neighbour strategies:

• prediction based automatic allocation

Automatic Neighbour Relation (ANR)