Overview

LTE Transport Network

Dimensioning

Volker Hoehn, Silvia Ricchi, VF- TSO-

Access – Design, Tools & Backhaul

1 Confidentiality level: C2
27 August 2014
Overview LTE Transport Network Dimensioning

Transport Network Understand

Architecture - what are the elements of the LTE Transport Network

LTE Roll-out Understand

characteristics - which input is needed for dimensioning.

Dimensioning rules Understand

- On how to dimension a LTE Transport Network

IP-addressing, Understand
Synchronisation - Additional requirements

Understand
Conclusion - Essence of Transport dimensioning

2 Confidentiality level: C2
27 August 2014
 LTE / Evolved Packet System (EPS)- Areas

E-UTRAN EPC

X2
eNode-B S1 SAE GW
X2

eNode-B eNode-B

X2 X2 MME
eNode-B
Access & Backhaul
Transport Network
E-UTRAN: Evolved UTRAN
EPC: Evolved Packet Core

Goal: Ensure End-to-End performance from E-UTRAN to EPC

3 Confidentiality level: C2
27 August 2014
 Transport Network
Architecture
LTE Transport Architecture Network
• During FY09/10: LTE Radio & Transport sharing group (leaded by Volker Hoehn)
engaged Access & Core Transport team (VTN A APU & VTN C CTTA) to identify the
Transport network design requirements for supporting LTE
• Transport Architecture Network defined and agreed within NGDI group

Æ VF current position is that all X2 traffic

must be authenticated through
the Sec GW .
Æ Encryption is not required

It will be based on a combination of Fibre, MW based solutions

(BEP2.0) and BEP1.0 (IP/MPLS Backhaul) aggregation as convergent
transport layer for 2G/3G/HSPA+/LTE enabling the LTE flat architecture
with the use of IP VPNs
4 Confidentiality level: C2
27 August 2014
 Transport Network towards Core
BEP2.0 used where fiber is not available
L2 trunk among BEP 1.0 equipment

Security
Gateway
Regional
Backhaul
National Core
MESN: Metro Ethernet

LTE
Tail Feeder BSC RNC
GW

Major usage of BEP 2.0 2G/3G/LTE site

TDM transport & MUX for 2G and 3G ATM
BEP 1.0
L2 transport & aggregation for 3G IP
Æ VF current position is that all X2 traffic must be authenticated through BEP 2.0 link
the Sec GW located sing the IpSec framework.
Æ Encryption is not required
5 Confidentiality level: C2
27 August 2014
 LTE Roll-out and
characteristics
LTE Roll out & LTE characteristic

LTE rollout
• Considering LTE basic configuration (2x2 MIMO), Traffic area Year 1 Year 2 Year 3 Year 4
LTE Rollout (input from Radio Design) has been Hot spots –Dense
identified for three different penetration scenarios: LTE 2600 2% 3% 5% 8%
Urban
Dense Urban, Urban and Rural.
Urban -Hot spots &
• Separated dimensioning study cases has been LTE 1800 0 10% 25% 50%
coverage
performed in each areas1 to evaluated the impact
on Access and Backhaul Rural -Hot spots &
LTE 800 5%* 15%* 40%* 70%*
coverage

(*) LTE800 is referred to the number of GSM sites

LTE characteristics
Application Scenario Rural Urban Dense
• LTE characteristics (input from Radio Design)
defined LTE throughput figures (DL average data Bandwidth (MHz) 10 10 20
rate and DL peak data rate) per each scenarios Average data rate cell 20 15 30
• To obtain the transport capacity for LTE, an DL throughput
overhead2 introduced by layers below IP has to be (Mb/s) (*)
added to the throughput figures (showed in the
table) Peak data rate cell DL 60 60 120
throughput (Mb/s)
• Taking advantage of overhead calculation example
provided by VF-DE, we assumed as realistic average Peak to average ratio 3 4 4
cases: 20% of overhead in case of IPsec and 10% of
overhead without IPsec 2. Overhead depends on packet size and IPsec support

6 Confidentiality level: C2
27 August 2014
 Dimensioning rules
Dimensioning rules

1. Identifying where and which concentration overbooking criteria has to be apply:

Access (last mile) dimensioned by peak1; and Backhaul based on statistical multiplexing gain

2. Defining the required transport capacity to support specific traffic scenarios

(simultaneous user; type of services, …) that the LTE nodeB shall support
– Due to lack of detail information on traffic demand two possible traffic cases have been identified:
Basic and Aggressive

– For Access TX, following traffic scenarios have been assumed:

Traffic cases for

Rural Urban Dense
Access
Bandwidth (MHz) 10 10 20
1 Peak data rate 2 per 1 Peak data rate per 1 Peak data rate per
Basic
site site site
(1 Peak data rate + 1 (2 Peak data rate + 1
1 Peak data rate per
Aggressive average data rate) average data rate)
site
per site per site

1. Peak is the maximum TX capacity required for connect LTE site.

2. Peak data rate: is the maximum data rate provided to the end user by the radio resources

7 Confidentiality level: C2
27 August 2014
Capacity required in Access Dimensioning rules

Basic Traffic case

Rural Rural Urban Dense
Application Scenario
(1 peak) (1 peak) (1 peak) (1 peak)
Bandwidth (MHz) 5 10 10 20
Peak cell DL throughput (Mb/s) with Ipsec 36 72 72 144
Peak cell DL throughput (Mb/s) no Ipsec 33 66 66 132
Average cell DL throughput (Mb/s) with Ipsec 9.6 24 18 36

Aggressive Traffic case

Urban
Rural Rural Dense
Application Scenario (1 peak +
(1 peak) (1 peak) (2 peak + 1 average)
1average)
Bandwidth (MHz) 5 10 10 20
Peak cell DL throughput (Mb/s) with Ipsec 36 72 90 324
Peak cell DL throughput (Mb/s) no Ipsec 33 66 82.5 297
Average cell DL throughput (Mb/s) with Ipsec 9.6 24 18 36

8 Confidentiality level: C2
27 August 2014
Example VF-DE: Dimensioning guideline_LTE introduction

Aggressive Traffic case_urban: (1 Peak data rate + 1 average data rate) per site

LTE800 LTE2600 3G-IP 3G 2G-IP 2G

Bandwidth 10 MHz 20 MHz

Peak datarate 72 Mbps 144 Mbps 25 Mbps 4 Mbps

cell DL throughput
Average datarate 24 Mbps 30 Mbps 5 Mbps 5-8 x 4 Mbps 2x
cell DL throughput + 2 x E1 E1 E1

LTE throughput figures including overhead (Ethernet/ IP/ IPSec/ UDP/ GTP)

9 Confidentiality level: C2
27 August 2014
 Link dimensioning daisy chain

Verfahren der maximalen Linkdimensionierung

Zusammenfassung (Addieren aller AVGs) aller an einen Link angeschlossenen RAN Netzelemente –
vom Regional Backhaul in Richtung Basisstation (Downlink) geschaut. Zusätzlich wird für das
Netzelement mit der höchsten erforderlichen Datenrate der PEAK Wert hinzugefügt.

1 x peak + 1 x peak + 1 x peak +

n x average n x average n x average Regional Backhaul
link 3 (SDH, ATMAS, Metro
link 1 link 2
Ethernet)
1 x LTE (10) 1 x LTE (20) 1 x 2G
usw…
1 x 3G 1 x 3G-IP 1 x 3G-IP

link 1:
max. Dimensionierung: = 96 Mbps + 8 x E1 = 112 Mbps = Peak + Average
link 2:
max. Dimensionierung: 24 Mbps + 8 x E1 + 174 Mbps + 5 Mbps + 2 x E1
= 203 Mbps + 10 x E1 = 223 Mbps
link 3:
max. Dimensionierung: 24 Mbps + 8 x E1 + 174 Mbps + 5 Mbps + 2 x E1 + 2 x E1 + 5 Mbps + 2 x E1
= 208 Mbps + 14 x E1 = 236 Mbps

10 Confidentiality level: C2
27 August 2014
Update of Dimensioning rules after 3 years LTE operation
Dimension Guideline FY2013/14 for new and upgrade RAN Equipment
LTE800 LTE2600 3G-Hybrid 3G-ATM 2G-IP 2G
Bandwidth 10 MHz 20 MHz

Peak datarate 72 Mbps 144 Mbps 62 Mbps 4 Mbps

cell DL throughput
Average datarate Node DL 26 Mbps 40 Mbps 8 Mbps 8 x E1 4 Mbps 2 x E1
throughput + 4 x E1
(6Mbps (3xE1
Average datarate Node DL 39 Mbps 60 Mbps 12 Mbps 8 x E1
>17 TRX) >17 TRX)
throughput for HOS-Nodes + 4 x E1

min. Transmission BW = max(peak BW) + ∑ avg. BW + ∑ TDM-BW

all Nodes all Nodes all Nodes

Summary of differencies between old and new dimension rules

¾ higher initial average traffic for LTE800/2600 and 3G than FY 12/13
¾ higher initial ATM/TDM Bandwidth for 3G-Hybrid due to use of 3rd Carrier
(needs additional Rel99 VCs with reservation Bandwidth)
¾ higher peak bandwidth for 3G due to the use of HSDPA
(consider default Shaping Bandwidth of 70 Mbps for 3G-NSN)
¾ no change for 2G dimension (number of E1 correlated with TRX)
 LTE Access Transmission – Synchronisation ( ref.: Kevin Brackpool)
• Synchronous Ethernet is the primary sync delivery mechanism (relies on
physical layer similar to existing TDM synch delivery)
• Problem when physical layer is not under operator control
• IEEE1588v2 Æ packet based sync distribution also phase
– Synchronisation option to be used but require additional hardware (master clock,
boundary clock etc.) and special access engineering for timing packets.

LTE Radio&Transport Design Standard

12 Volker Hoehn,,VTN-A-Design Confidentiality level: C2
27 August 2014
Example for Sync Distribution with IEEE 1588v2 (ptp)

S -1
Eo T M
S
x
N

13 Confidentiality level: C2
27 August 2014
LTE Access Transmission - IP addressing and eNB connectivity

• At least two inner (S1/X2 and OAM) and two outer (IPSec tunnel) IP
addresses are needed per eNB plus one for Synch IP
– IPSec tunnel IP addresses can be used repeatedly per Security GW region
– „Inner IP“ addresses should be unique – they are seen by EPC

14 Confidentiality level: C2
27 August 2014
IP/L3-Konfiguration der eNBs

• Die eNB benötigt 5 IP-Adressen: 192.168.c.0/23

.c.4
.b.4
– Synch IP (wird vom Synch Server aus mit Time- 172.26.a.b /32
Paketen bedient) Traffic VLAN 302
– IPSec Tunnel-Endpunkt Adresse für LTE 10.99.y.0/23
10.99.x.0/23 .x.4 .y.4
Wirkverkehr (S1/X2)
O&M
– IPSec Tunnel-Endpunkt Adresse für OAM Verkehr VLAN 301
(eindeutig)
192.168.d.0/23 .d.4 VLAN 300
– Innere Adresse für Wirkverkehr („global“ eindeutig) Sync
– Innere Adresse für OAM Verkehr („global“ eindeutig)

• Vorgesehen sind bis zum MESN Standort

/23er Netzmasken für eNBs Æ 510 eNBs Nur logische
Trennung

• Rollout von Security Gateways

– Initial 2 Stück (1xErfurt / 1x Kornwestheim/Ericsson)
– Bis Ende FY2010/11 werden 8 SecGW (1 pro 4
Region) geplant
– Nachfolgend wird weiter in die PoC Standorte
dezentralisiert

Access Design
Confidentiality level: C2
November 12, 2010
Solutions- MW Ethernet (BEP2.0) and BEP2.0+
BEP2.0 used where fiber is not available
• BEP2.0 usage: L2 trunk among BEP 1.0 equipment

– to replace Legacy PDH MW

– In high capacity sites on tail/ feeder in urban/rural
– Up to 400 Mbps in 56 MHz channel (AM) Regional
Backhaul National Core
– Support 2G/3G/HSPA/LTE

• BEP2.0 vendors: Tail Feeder

LTE
BSC RNC GW
2G/3G site

BEP2.0+
– NSN, Huawei, SAE
BEP 1.0
Major usage of BEP 2.0
TDM transport & MUX for 2G and 3G ATM BEP 2.0 link
L2 transport & aggregation for 3G IP

• BEP2.0+ is an optimization of BEP 2.0 to:

• avoid further deploying of legacy SDH MW
• provide native Ethernet (GE) interfaces towards BEP 1.0 (MPLS routers)
• provide up to 500 Mbps in 56 MHz channel
• BEP 2.0+ will have the following additional key features:
• XPIC to get maximum flexibility in the radio frequency planning
• 2+0 bundling of two radio channels at L1 for providing a single GE pipe towards BEP 1.0
• Packet compression for increasing capacity throughput average (gain of 20 - 40%*)
(*) throughput depending on mix of data services and HC feature capabilities in MW link
Blueprint and guideline available
16 Confidentiality level: C2
27 August 2014
BEP2.0 capacity performance
Following table shows net throughput overview (Mbps) per channel spacing for each
modulation

Net Throughput (Mbps) with AM

4QAM 16QAM 64QAM 128QAM 256QAM

7 MHz 11 21 32 38 44

14 MHz 21 42 66 78 90

28 MHz 43 86 135 158 183

56 MHz 85 169 265 313 363

These figures are taken from BEP2.0 Vendor selected (Huawei, NSN and SIAE)

9 Increase channel efficiency using Adaptive Modulation (up to 256-QAM)

9 Achievable performances: 180 (360)Mbps in 28 (56) MHz channel (AM)

17 Confidentiality level: C2
27 August 2014
Backhaul Evolution Programme R1.0 (BEP1.0)
• Introduction of IP/MPLS in the Backhaul Transport network
• Support over the same IP/MPLS network all existing and new services and any type
of radio sites providing QoS:
– legacy TDM (2G) , ATM (3G) services and IP/Ethernet services
– BTS, 3G Node B/HSPA+ and LTE eNode Bs

• Support RAN IP migration and Fixed Mobile Convergence

• BEP R1.0 over Access & Backhaul to be future-proof architecture towards all IP
• BEP1.0 vendors:
– Tellabs (2007) and Huawei (2008)

IP/MPLS
• Security GW can be a clear demarcation point between Backhaul
Backhaul and Core transport networks (located at PoC1)
• S1 interface (used to connect eNBs to MME and S-GW in the IP/MPLS
core) is encrypted with IPsec
• Requirement for X2 interface (used between adjacent eNBs) is Core
not encrypted with IPsec
• LTE transport means a 3 steps process:
1.eNB Authentication
2.eNB Auto configuration
3.Signaling/user traffic flow between eNB and MME, S-GW

BEP1.0 architecture for LTE

Blueprint and guideline
LTE Radio&Transport available
Design Standard
18 Volker Hoehn,,VTN-A-Design Confidentiality level: C2
MPLS: Multi-Protocol Label Switching
27 August 2014
 Security Gateway - CISCO – 7600 series (13 Slot)
Cisco 7600 the only platform to currently support all needed features

WSG (SAMI) provides

encryption

57 locations each with

2 x CISCO 7613 Chassis - each includes:
• 6x WSG (SAMI) up to 5.0 Gbit/sec per board
(using SHA-1, AES128, packet size dependent)
• 6 x10GE ports / 6 x 1 GE ports
• High avialability configuration
- VF current position is that all X2 traffic must be authenticated through the Sec GW located sing the IpSec framework.
- Encryption is not required.
- Latency is not an issue within the Sec GW box (100 Micro sec with Juniper and Cisco)
- Main issue is Network topology and due to the fact that IpSec in eNode B is done as a S/W task.

19 Confidentiality level: C2
27 August 2014
Fibre to Points of Concentrations
• Deploy Fibre to Points of Concentration (PoC) Transmission Network
based on Traffic demand and positive business evolution
Legacy MW
case BEP2.0 link
Fibre
• PoC2:
– Fiber is used to replace SDH microwave where
is available (urban/dense urban). BEP2.0+ can be
used to provide an alternative upgrade path of fiber
PoC3
in the regional backhaul Dark fibre
/
– Fiber and MW Ethernet can be selected based on Managed
demand service
network PoC2
• PoC3:
– MW Ethernet (BEP2.0) support HSPA+ and LTE
PoC1
– Fibre could be required as traffic demand grow to RNC/BSC
better experience HSPA+ and LTE rates. Careful
consideration for cost (like Fiber to the site)

Fibre introduction into the most loaded parts of the network

20 Confidentiality level: C2
27 August 2014
Other wireless solutions
• Full Outdoor solutions (2.6 – 80 GHz)
– to be a strategic solution for micro / pico / femto sites Small site backhaul (i.e lamppost)
– for tail connections to full IP radio sites (very small distance in urban)
– Candidate technology: for no LOS (<6 GHz up to 150 Mbps) and for LOS (60 GHz unlicensed up to 1
Gbps)

Fiber
site infrastructure

BEP 2.0 Links

Very light

Full Outdoor
Regional Backhaul

LTE
GW
Tail Feeder BSC RNC

Regional backhauling proposal

• Gigabit radios with MIMO (6 – 42 GHz) Gigabit radio link

– for Gigabit long links in rural areas no distance limitations

– complementary solution to dark fiber in the regional backhaul
– MIMO to overcome spectrum congestions in the lower frequency bands
• E band (70 & 80 GHz) EBand

– Used for connecting a series of micro sites

– for Gigabit (1 – 2.5 Gbps) short links in urban areas (1 to 2 to 4km)
– complementary solution to dark fiber in the regional backhaul
21 Confidentiality level: C2
27 August 2014
Access Technology summary
Solution Rate Applicability & product
• Urban/ Rural
BEP2.0 Up to 400 Mbps • full outdoor (line of sight)
• product available from Q4 2010
• Urban/ Rural
BEP2.0+ up to 500 Mbps • Regional Backhaul
• product availability (by mid 2011)
• Urban/ Dense
Fiber 100÷1000 Mbps • outdoor NT
• cost & fiber provider
• Urban
Full Outdoor 150÷1000 Mbps • (2.6 – 80 GHz) and LOS/ no LOS
• product availability (from end 2011)
• Rural
• Regional Backhaul
Gigabit Radio Up to 1 Gbps
• (6 – 42 GHz)
• product availability (from mid 2012)
• Urban (max 2km)
• Regional Backhaul
Eband 1 – 2.5 Gbps • (70– 80 GHz)
• product availability (from 2012 NSN;
2013 for the other vendors)

22 Confidentiality level: C2
27 August 2014
Conclusions
Impact on Transport dimensioning study
• changing LTE throughput
• changing LTE Roll out
• taking Real traffic demand (that brings to the different overhead)

Recommended Transport technologies

• Fiber is considered unlimited capacity
• MW Ethernet (BEP2.0) could be used in the Tail & Feeder depending on channel availability different
level of capacity up to 400Mb/s in 56 MHz. BEP2.0 + can be used in Regional Backhaul to replace
legacy SDH MW
• BEP1.0 is future proof aggregation technologies with different platform sizes to support any traffic
scenario in Access and Backhaul area
• Ethernet based Managed Service where Self Backhauling is not feasible (Dense and Urban)

Dimensioning rules
• Access dimensioned by peak and Backhaul based on statistical multiplexing gain
• Enlarge backhauling closer to the sites (with BEP1.0 and/or BEP2.0) in to benefit at an earlier stage of
the multiplexing gain provided by these technologies
• Build the TX network with suggested technologies that can cope with LTE evolution

Start LTE deployment with Basic scenario for a TX cost effectiveness

and move to Aggressive when traffic demand requires it
23 Confidentiality level: C2
27 August 2014
ANNEX

24 Confidentiality level: C2
27 August 2014
eNB connection for LTE- implementation example
• eNB has a DUL unit for each frequency, plus SIU as mobile site router
• S1/X2 connection uses IPSec/IP/Ethernet.
• SIU converts IEEE1588v2 based IP synchronisation to a proper sync signal
for eNB

C- VLANs
301 (O&M)
302 (S1/X2) S- VLAN 3999 (z.B.)

Microwave …simplified…
GE
eNB C-VLANs
DUL 800 300 ( Sync)
SIU 301 (O&M)
302 (S1/X2)
303 (O&M)
304 (S1/X2)

GE Access
Sync Transmission
Y- Kabel

Near End Far End

BEP R1
BEP R2
GE
C- VLANs
eNB 303 (O&M)
304 (S1/X2)
DUL 2600 SIU: Site Integration Unit
DUL: Digital Unit for LTE

25 Confidentiality level: C2
27 August 2014
Abbreviations

VLAN Virtual LAN

VLL Virtual Leased Line (L2)

MESN Metro Ethernet Switch

Network
EBS Ethernet Business Service

NTP Network Time Protocol

PoC Point of Concentration

(Sammler)
PoC3 Heute typisch PDH
Vorsammler (sammelt
wenige Mobil-Standorte;
<=20)
PoC2 (SDH/ATM/ME) Heute typisch SDH-
Sammler oder ATMAS
Knoten; sammelt typisch
>=20 Mobil-Standorte auf)
PoC1 BSC oder RNC Site;
MSC/MGW/POP Site
PTP Precision Time Protocol

26 Confidentiality level: C2
27 August 2014