lte-design-and-deployment-strategies-zeljko-savic.pdf
AliAlwesabi
30 views
79 slides
May 10, 2024
Slide 1 of 79
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
About This Presentation
lte-design-and-deployment-strategies-zeljko-savic.pdf
Slide Content
Zeljko Savic, Systems Engineer SP
[email protected]
LTE Design and
Deployment Strategies
Right Acronym for LTE
LTE
Long Term Employment
Long Term Evolution
Life Time Employment
[email protected]
LTE Design and
Deployment Strategies
Right Acronym for LTE
LTE
Long Term Employment
Long Term Evolution
Life Time Employment
© 2011 Cisco and/or its affiliates. All rights reserved.
2
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
LTE Security
LTE Deployment Strategies
Summary, References
Agenda
2
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
LTE Security
LTE Deployment Strategies
Summary, References
Agenda
© 2011 Cisco and/or its affiliates. All rights reserved.
3
Mobile Broadband Devices and What they Do?
Dongle (Notepad/netbooks) & Smartphone ~80% of total traffic
Video(66%), Mobile Web/data (20%), Peer-to-Peer (6%)
Key issue
Managing OTT video including other Apps efficiently
Contents caching and delivering close to edge
Local breakout using Mobile Edge Gateway
3
Mobile Broadband Devices and What they Do?
Dongle (Notepad/netbooks) & Smartphone ~80% of total traffic
Video(66%), Mobile Web/data (20%), Peer-to-Peer (6%)
Key issue
Managing OTT video including other Apps efficiently
Contents caching and delivering close to edge
Local breakout using Mobile Edge Gateway
© 2011 Cisco and/or its affiliates. All rights reserved.
4
Global mobile data traffic grew 2.6-fold in 2010, nearly tripling for the third year in a row
Last year's mobile data traffic was three times the size of the entire global Internet in 2000. Global mobile data traffic in 2010 (237 petabytes per month) was over
three times greater than the total global Internet traffic in 2000 (75 petabytesper month).
Mobile video traffic will exceed 50 percent for the first time in 2011. Mobile video traffic was 49.8 percent of total mobile data traffic at the end of 2010, and will
account for 52.8 percent of traffic by the end of 2011.
Mobile network connection speeds doubled in 2010. Globally, the average mobile network downstream speed in2010 was 215 kilobits per second (kbps), up from 101
kbps in 2009. The average mobile network connection speed for smartphones in 2010 was 1040 kbps, up from 625 kbps in 2009.
The top 1 percent of mobile data subscribers generate over 20 percent of mobile data traffic, down from 30percent 1 year ago. According to a mobile data usage
study conducted by Cisco, mobile data traffic has evened out over the last year and now matches the 1:20 ratio that has been tru e of fixed networks for several years.
Similarly, the top 10 percent of mobile data subscribers now generate approximately 60 percent of mobile data traffic, down from70 percent at the beginning of the year.
Average smartphoneusage doubled in 2010. The average amount of traffic per smartphone in 2010 was 79MBper month, up from 35 MB per month in 2009.
Smartphonesrepresent only 13 percent of total global handsets in use today, but they represent over 78percent of total global handset traffic. In 2010, the
typical smartphonegenerated 24 times more mobile data traffic (79 MB per month) than the typical basic-feature cell phone (which generated only 3.3 MB per month of
mobile data traffic).
Globally, 31 percent of smartphonetraffic was offloaded onto the fixed network through dual-mode or femtocellin 2010. Last year, 14.3 petabytesof smartphone
and tablet traffic were offloaded onto the fixed network each month. Without offload, traffic originating from smartphones and tablets would have been 51 petabytes per
month rather than 37 petabytesper month in 2010.
Android approaches iPhonelevels of data use. At the beginning of the year, iPhoneconsumption was at least 4times higher than that of any other smartphone
platform. Toward the end of the year, iPhoneconsumption was only 1.75 times higher than that of the second-highest platform, Android.
In 2010, 3 million tablets were connected to the mobile network, and each tablet generated 5 times more traffic than the averagesmartphone. In 2010, mobile
data traffic per tablet was 405 MB per month, compared to 79MB per month per smartphone.
There were 94 million laptops on the mobile network in 2010, and each laptop generated 22 times more traffic than the averagesmartphone. Mobile data traffic
per laptop was 1.7 GB per month, up 49 percent from 1.1 GB per month in 2009.
Nonsmartphoneusage increased 2.2-fold to 3.3 MB per month in 2010, compared to 1.5 MB per month in 2009 . Basic handsets still make up the vast majority of
devices on the network (87 percent).
From Cisco VNIReport…
4
Global mobile data traffic grew 2.6-fold in 2010, nearly tripling for the third year in a row
Last year's mobile data traffic was three times the size of the entire global Internet in 2000. Global mobile data traffic in 2010 (237 petabytes per month) was over
three times greater than the total global Internet traffic in 2000 (75 petabytesper month).
Mobile video traffic will exceed 50 percent for the first time in 2011. Mobile video traffic was 49.8 percent of total mobile data traffic at the end of 2010, and will
account for 52.8 percent of traffic by the end of 2011.
Mobile network connection speeds doubled in 2010. Globally, the average mobile network downstream speed in2010 was 215 kilobits per second (kbps), up from 101
kbps in 2009. The average mobile network connection speed for smartphones in 2010 was 1040 kbps, up from 625 kbps in 2009.
The top 1 percent of mobile data subscribers generate over 20 percent of mobile data traffic, down from 30percent 1 year ago. According to a mobile data usage
study conducted by Cisco, mobile data traffic has evened out over the last year and now matches the 1:20 ratio that has been tru e of fixed networks for several years.
Similarly, the top 10 percent of mobile data subscribers now generate approximately 60 percent of mobile data traffic, down from70 percent at the beginning of the year.
Average smartphoneusage doubled in 2010. The average amount of traffic per smartphone in 2010 was 79MBper month, up from 35 MB per month in 2009.
Smartphonesrepresent only 13 percent of total global handsets in use today, but they represent over 78percent of total global handset traffic. In 2010, the
typical smartphonegenerated 24 times more mobile data traffic (79 MB per month) than the typical basic-feature cell phone (which generated only 3.3 MB per month of
mobile data traffic).
Globally, 31 percent of smartphonetraffic was offloaded onto the fixed network through dual-mode or femtocellin 2010. Last year, 14.3 petabytesof smartphone
and tablet traffic were offloaded onto the fixed network each month. Without offload, traffic originating from smartphones and tablets would have been 51 petabytes per
month rather than 37 petabytesper month in 2010.
Android approaches iPhonelevels of data use. At the beginning of the year, iPhoneconsumption was at least 4times higher than that of any other smartphone
platform. Toward the end of the year, iPhoneconsumption was only 1.75 times higher than that of the second-highest platform, Android.
In 2010, 3 million tablets were connected to the mobile network, and each tablet generated 5 times more traffic than the averagesmartphone. In 2010, mobile
data traffic per tablet was 405 MB per month, compared to 79MB per month per smartphone.
There were 94 million laptops on the mobile network in 2010, and each laptop generated 22 times more traffic than the averagesmartphone. Mobile data traffic
per laptop was 1.7 GB per month, up 49 percent from 1.1 GB per month in 2009.
Nonsmartphoneusage increased 2.2-fold to 3.3 MB per month in 2010, compared to 1.5 MB per month in 2009 . Basic handsets still make up the vast majority of
devices on the network (87 percent).
From Cisco VNIReport…
© 2011 Cisco and/or its affiliates. All rights reserved.
5
There are 48 million people in the world who have mobile phones, even though they do not have electricity athome. The mobile network has extended beyond the
boundaries of the power grid.
Global mobile data traffic will increase 26-fold between 2010 and 2015. Mobile data traffic will grow at a compound annual growth rate ( CAGR) of 92 percent from
2010 to 2015, reaching 6.3 exabytes per month by 2015.
There will be nearly one mobile deviceper capitaby 2015. There will be over 7.1 billion mobile-connected devices, including machine -to-machine (M2M) modules, in
2015-approximately equal to the world's population in2015 (7.2 billion).
Mobile network connection speeds will increase 10-fold by 2015 . The average mobile network connection speed (215 kbps in 2010) will grow at a compound annual
growth rate of 60 percent, and will exceed 2.2 megabits per second (Mbps) in 2015.
Two-thirds of the world's mobile data traffic will be video by 2015. Mobile video will more than double every year between 2010 and 2015. Mobile video has the
highest growth rate of any application category measured within the Cisco VNI forecast at this time.
Mobile-connected tablets will generate as much traffic in 2015 as the entire global mobile network in 2010. The amount of mobile data traffic generated by tablets in
2015 (248 petabytes per month) will be approximately equal to the total amount of global mobile data traffic in 2010 (242 petabytes per month). The same will be true of
M2Mtraffic, which will reach 295 petabytesper month in 2015.
The average smartphonewill generate 1.3 GB of traffic per month in 2015, a 16-fold increase over the 2010 average of 79 MB per month. Aggregate smartphone
traffic in 2015 will be 47 times greater than it is today, with aCAGRof 116 percent.
By 2015, over 800 million terabytes of mobile data traffic will be offloaded to the fixed network by means ofdual-mode devices and femtocells. Without dual -
mode and femtocell offload of smartphone and tablet traffic, total mobile data traffic would reach 7.1 exabytes per month in 2015, growing at a CAGRof 95 percent.
The Middle East and Africa will have the strongest mobile data traffic growth of any region at 129 percent CAGR , followed by Latin America at 111 percent and
Central and Eastern Europe at 102 percent.
There will be 788 million mobile-only Internet users by 2015. The mobile-only Internet population will grow 56-fold from 14 million at the end of 2010 to 788 million by
the end of 2015.
The mobile network will break the electricity barrier in more than 4 major regions by 2015. By 2015, 4 major regions (Sub-Saharan Africa, Southeast Asia, South
Asia, and the Middle East) and 40 countries (including India, Indonesia, and Nigeria) will have more people with mobile network access than with access to electricity at
home. The off-grid, on-net population will reach 138 million by 2015.
From Cisco VNIReport…
5
There are 48 million people in the world who have mobile phones, even though they do not have electricity athome. The mobile network has extended beyond the
boundaries of the power grid.
Global mobile data traffic will increase 26-fold between 2010 and 2015. Mobile data traffic will grow at a compound annual growth rate ( CAGR) of 92 percent from
2010 to 2015, reaching 6.3 exabytes per month by 2015.
There will be nearly one mobile deviceper capitaby 2015. There will be over 7.1 billion mobile-connected devices, including machine -to-machine (M2M) modules, in
2015-approximately equal to the world's population in2015 (7.2 billion).
Mobile network connection speeds will increase 10-fold by 2015 . The average mobile network connection speed (215 kbps in 2010) will grow at a compound annual
growth rate of 60 percent, and will exceed 2.2 megabits per second (Mbps) in 2015.
Two-thirds of the world's mobile data traffic will be video by 2015. Mobile video will more than double every year between 2010 and 2015. Mobile video has the
highest growth rate of any application category measured within the Cisco VNI forecast at this time.
Mobile-connected tablets will generate as much traffic in 2015 as the entire global mobile network in 2010. The amount of mobile data traffic generated by tablets in
2015 (248 petabytes per month) will be approximately equal to the total amount of global mobile data traffic in 2010 (242 petabytes per month). The same will be true of
M2Mtraffic, which will reach 295 petabytesper month in 2015.
The average smartphonewill generate 1.3 GB of traffic per month in 2015, a 16-fold increase over the 2010 average of 79 MB per month. Aggregate smartphone
traffic in 2015 will be 47 times greater than it is today, with aCAGRof 116 percent.
By 2015, over 800 million terabytes of mobile data traffic will be offloaded to the fixed network by means ofdual-mode devices and femtocells. Without dual -
mode and femtocell offload of smartphone and tablet traffic, total mobile data traffic would reach 7.1 exabytes per month in 2015, growing at a CAGRof 95 percent.
The Middle East and Africa will have the strongest mobile data traffic growth of any region at 129 percent CAGR , followed by Latin America at 111 percent and
Central and Eastern Europe at 102 percent.
There will be 788 million mobile-only Internet users by 2015. The mobile-only Internet population will grow 56-fold from 14 million at the end of 2010 to 788 million by
the end of 2015.
The mobile network will break the electricity barrier in more than 4 major regions by 2015. By 2015, 4 major regions (Sub-Saharan Africa, Southeast Asia, South
Asia, and the Middle East) and 40 countries (including India, Indonesia, and Nigeria) will have more people with mobile network access than with access to electricity at
home. The off-grid, on-net population will reach 138 million by 2015.
From Cisco VNIReport…
© 2011 Cisco and/or its affiliates. All rights reserved.
6
Top 10% Devices generate 60% of total traffic
Android is catching fast iOSwith iPhone for usage
Device operating system & Apps have unique characteristics
impacting signaling and bearer traffic
Challenge of Smartphone
Radio signaling overload, simultaneous device updates
Bandwidth hogging, Concurrent flows, Keeping NAT pin holes
Malware (DOS/DDoS) attack
Device Comparisons
Cisco VNIReport 2010-2015
6
Top 10% Devices generate 60% of total traffic
Android is catching fast iOSwith iPhone for usage
Device operating system & Apps have unique characteristics
impacting signaling and bearer traffic
Challenge of Smartphone
Radio signaling overload, simultaneous device updates
Bandwidth hogging, Concurrent flows, Keeping NAT pin holes
Malware (DOS/DDoS) attack
Device Comparisons
Cisco VNIReport 2010-2015
© 2011 Cisco and/or its affiliates. All rights reserved.
7
Mobile data offload free- up macro network
Enhance user experience due to more bandwidth
Offload is integral part of overall design
Offload technologies –SP WiFi, Femto etc…
Benefit out-weight network complexities due to offload
Mobile Data offload
7
Mobile data offload free- up macro network
Enhance user experience due to more bandwidth
Offload is integral part of overall design
Offload technologies –SP WiFi, Femto etc…
Benefit out-weight network complexities due to offload
Mobile Data offload
© 2011 Cisco and/or its affiliates. All rights reserved.
8
ARPU
(Revenue)
Data Traffic (Cost)
Profitability
Gap
Increase Revenue
In-house Apps
B2B2CBusiness Model
Enable Content and Partnerships
Reduce Costs
Manage “Over The Top”
Offload internet traffic at edge
Optimal use of expensive assets
Improve Experience
Innovative services
3-screen experience, session
shifting quality of video experience
MobileOperator’sChallengesandOpportunity
8
ARPU
(Revenue)
Data Traffic (Cost)
Profitability
Gap
Increase Revenue
In-house Apps
B2B2CBusiness Model
Enable Content and Partnerships
Reduce Costs
Manage “Over The Top”
Offload internet traffic at edge
Optimal use of expensive assets
Improve Experience
Innovative services
3-screen experience, session
shifting quality of video experience
MobileOperator’sChallengesandOpportunity
© 2011 Cisco and/or its affiliates. All rights reserved.
9
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
9
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
© 2011 Cisco and/or its affiliates. All rights reserved.
10
Mobile Network Evolution –Convergence to LTE*
1xRTT
EDGE
<1999 2000-02 2006-07
Voice
Data (9.6 -56k)
Voice
Data (9.6 -56k)
Data (DL 2.4M)Voice 2x cap
Data (144k)
Data
(DL/UL 20/80k)
Voice
(DL/UL 384/384k)
e-EDGE
UMBIS-95
2008-09 20010-11
LTE
2012+
(DL 1Mbps)
GSM
WiMAX
EV-DO RevB
Multi-carrier Data (14.7M)
HSPA+
LTE
Advanced
3G R99 HSDPA HSUPA
2003-04
Enhanced modulation (DL 384k)
EV-DO RevA
(DL/UL 100/50M)
Optimized DL (14.4M)
Optimized UL
(5.7M)
MIMO, 64QAM (DL/UL 42/11M)
GPRS
3GPP2 Track
3GPP Track
Mobile Network Transformation to All IP
Architecture Harmonization
(3GPP R8) (3GPP R10+)
* Actual speed depend upon many factors
10
Mobile Network Evolution –Convergence to LTE*
1xRTT
EDGE
<1999 2000-02 2006-07
Voice
Data (9.6 -56k)
Voice
Data (9.6 -56k)
Data (DL 2.4M)Voice 2x cap
Data (144k)
Data
(DL/UL 20/80k)
Voice
(DL/UL 384/384k)
e-EDGE
UMBIS-95
2008-09 20010-11
LTE
2012+
(DL 1Mbps)
GSM
WiMAX
EV-DO RevB
Multi-carrier Data (14.7M)
HSPA+
LTE
Advanced
3G R99 HSDPA HSUPA
2003-04
Enhanced modulation (DL 384k)
EV-DO RevA
(DL/UL 100/50M)
Optimized DL (14.4M)
Optimized UL
(5.7M)
MIMO, 64QAM (DL/UL 42/11M)
GPRS
3GPP2 Track
3GPP Track
Mobile Network Transformation to All IP
Architecture Harmonization
(3GPP R8) (3GPP R10+)
* Actual speed depend upon many factors
© 2011 Cisco and/or its affiliates. All rights reserved.
11
Hierarchical Architecture
National
Regional
Market
GGSN
SGSN
MSC
BSC
IP
TDM
FR/TDM
BTS
2G/2.5G 3G UTRAN
GGSN
MSC
RNC
IP
ATM
IP
NB
SGSN
3.5GUTRAN
GGSN
MSC
RNC
IP
IP
IP
NB
SGSN
LTE E-UTRAN
HSS
PCRF
SGW
MME
IP
IP
eNB
PGW
MME –Mobility Management Entity, SGW – Serving Gateway, PGW – PDN Gateway
11
Hierarchical Architecture
National
Regional
Market
GGSN
SGSN
MSC
BSC
IP
TDM
FR/TDM
BTS
2G/2.5G 3G UTRAN
GGSN
MSC
RNC
IP
ATM
IP
NB
SGSN
3.5GUTRAN
GGSN
MSC
RNC
IP
IP
IP
NB
SGSN
LTE E-UTRAN
HSS
PCRF
SGW
MME
IP
IP
eNB
PGW
MME –Mobility Management Entity, SGW – Serving Gateway, PGW – PDN Gateway
© 2011 Cisco and/or its affiliates. All rights reserved.
12
LTE Functional Migration from 3G
Backhaul PDSN RNCBS
PCRF
Operator’s
IP Services
HLR
AAA
UE
Home Agent
MSC
eNodeB
RNC/PDSN (Control)
PDSN (Bearer)
MME
Serving Gateway
HSS
PDN Gateway
Authentication (Optional)
CDMA to LTE Migration
Signaling
Bearer
Backhaul SGSN RNCBS
PCRF
Operator’s IP Services
HLR
AAA
UE
GGSN
MSC
eNodeB
SGSN/RNC (Control)
SGSN (Bearer)
MME
Serving Gateway
HSS
PDN Gateway
Authentication (Optional)
UMTS to LTE Migration
Signaling
Bearer
12
LTE Functional Migration from 3G
Backhaul PDSN RNCBS
PCRF
Operator’s
IP Services
HLR
AAA
UE
Home Agent
MSC
eNodeB
RNC/PDSN (Control)
PDSN (Bearer)
MME
Serving Gateway
HSS
PDN Gateway
Authentication (Optional)
CDMA to LTE Migration
Signaling
Bearer
Backhaul SGSN RNCBS
PCRF
Operator’s IP Services
HLR
AAA
UE
GGSN
MSC
eNodeB
SGSN/RNC (Control)
SGSN (Bearer)
MME
Serving Gateway
HSS
PDN Gateway
Authentication (Optional)
UMTS to LTE Migration
Signaling
Bearer
© 2011 Cisco and/or its affiliates. All rights reserved.
13
LTE Functional Migration from 3G
LTE Term CDMAEquivalent UMTS Equivalent
eUTRAN (Evolved Universal
Terrestrial Radio Access Network)
AN (Access Network) UTRAN
eNode B (Evolved Node B) Base station + RNC Base station+ RNC
EPC (Evolved Packet Core) PDN (Packet Data Network)PDN
MME (Mobility Management Entity)RNC+ PDSN (Control part)SGSN(Control Part)
SGW (Serving Gateway) PDSN + PCF(Bearer part)SGSN (BearerPart)
PDN GW (Packet Data Network
Gateway)
HA (Home Agent) GGSN(GatewayGPRS Support
Node)
HSS (Home Subscriber System) AAA + HLR AAA + HLR
S1-MME (eNode B <-> MME for
Control)
A10/ A11/ A12 Iu
S1-U (eNode B <-> SGWfor
Bearer)
A10+ R-P Session Gn
S5/S8Bearer (SGW<-> PDNGW)MIP (Mobile IP Tunnel) Gn,Gb
EPS Bearer Service (E2E traffic
path between UE and PDN GW)
PPP + MIP PDP Context
13
LTE Functional Migration from 3G
LTE Term CDMAEquivalent UMTS Equivalent
eUTRAN (Evolved Universal
Terrestrial Radio Access Network)
AN (Access Network) UTRAN
eNode B (Evolved Node B) Base station + RNC Base station+ RNC
EPC (Evolved Packet Core) PDN (Packet Data Network)PDN
MME (Mobility Management Entity)RNC+ PDSN (Control part)SGSN(Control Part)
SGW (Serving Gateway) PDSN + PCF(Bearer part)SGSN (BearerPart)
PDN GW (Packet Data Network
Gateway)
HA (Home Agent) GGSN(GatewayGPRS Support
Node)
HSS (Home Subscriber System) AAA + HLR AAA + HLR
S1-MME (eNode B <-> MME for
Control)
A10/ A11/ A12 Iu
S1-U (eNode B <-> SGWfor
Bearer)
A10+ R-P Session Gn
S5/S8Bearer (SGW<-> PDNGW)MIP (Mobile IP Tunnel) Gn,Gb
EPS Bearer Service (E2E traffic
path between UE and PDN GW)
PPP + MIP PDP Context
© 2011 Cisco and/or its affiliates. All rights reserved.
14
LTE: New Terminologies*
*Some of the terms are known to UMTS operators, but new to CDMA Operators
LTE Term Meaning
AccessPoint Name (APN) Identifies an IP packet datanetwork (PDN)and service type
providedby the PDN to that user’s session.
PDNConnection
The Association between an UE and PDN (APN)
represented by one IPv4 Address and/or one IPv6 Prefix
GPRSTunneling Protocol (GTP)Signaling and Tunneling protocol fordata (between eNodeB,
SGW, and PGW)
EPS Bearer
An EPS bearer uniquely identifies traffic flows that receive a
common QoS treatment between UE and PDN-GW
Default Bearer First one to get established and remains established
throughout the lifetime of PDN Connection.
DedicatedBearer Additional bearer(other than default), created for a PDN
connection to provide specific QoS treatment for Apps
TrackingArea Update (TAU) Signaling Procedure performedby the UE to move between
MMEs
QoS ClassIndicator (QCI) Fieldindicating type of service associated with a data packet.
Traffic Flow Template (TFT) Atraffic filter that identifies an application class. This is
associated with a Dedicated Bearer and QCI.
14
LTE: New Terminologies*
*Some of the terms are known to UMTS operators, but new to CDMA Operators
LTE Term Meaning
AccessPoint Name (APN) Identifies an IP packet datanetwork (PDN)and service type
providedby the PDN to that user’s session.
PDNConnection
The Association between an UE and PDN (APN)
represented by one IPv4 Address and/or one IPv6 Prefix
GPRSTunneling Protocol (GTP)Signaling and Tunneling protocol fordata (between eNodeB,
SGW, and PGW)
EPS Bearer
An EPS bearer uniquely identifies traffic flows that receive a
common QoS treatment between UE and PDN-GW
Default Bearer First one to get established and remains established
throughout the lifetime of PDN Connection.
DedicatedBearer Additional bearer(other than default), created for a PDN
connection to provide specific QoS treatment for Apps
TrackingArea Update (TAU) Signaling Procedure performedby the UE to move between
MMEs
QoS ClassIndicator (QCI) Fieldindicating type of service associated with a data packet.
Traffic Flow Template (TFT) Atraffic filter that identifies an application class. This is
associated with a Dedicated Bearer and QCI.
© 2011 Cisco and/or its affiliates. All rights reserved.
15
LTE: New Terminologies*
*Some of the terms are known to UMTS operators, but new to CDMA Operators
LTE Term Meaning
Guaranteed Bit rate (GBR)
Bearer
Dedicated network resources
Allocatedpermanently at bearer establishment/modification
Non-Guaranteed Bit rate
(non- GBR) Bearer
No dedicated network resource are reserved
Default bearer is always non- GBR Bearer
APN-AMBR Aggregated maximum bit rate associated with all the non- GBR
bearers across all PDN connections connected to given APN.
Stored in HSS/HLR per APN
Not applicableto GBR bearers
UE-AMBR Aggregated maximum bit rate for UE
Subscription parameter and stored in HSS/HLR per UE
QoS Access agnostic QoS definition
QoS Class Identifier (QCI)
Allocation and Retention Priority
Guaranteed and Maximum Bit Rates
15
LTE: New Terminologies*
*Some of the terms are known to UMTS operators, but new to CDMA Operators
LTE Term Meaning
Guaranteed Bit rate (GBR)
Bearer
Dedicated network resources
Allocatedpermanently at bearer establishment/modification
Non-Guaranteed Bit rate
(non- GBR) Bearer
No dedicated network resource are reserved
Default bearer is always non- GBR Bearer
APN-AMBR Aggregated maximum bit rate associated with all the non- GBR
bearers across all PDN connections connected to given APN.
Stored in HSS/HLR per APN
Not applicableto GBR bearers
UE-AMBR Aggregated maximum bit rate for UE
Subscription parameter and stored in HSS/HLR per UE
QoS Access agnostic QoS definition
QoS Class Identifier (QCI)
Allocation and Retention Priority
Guaranteed and Maximum Bit Rates
© 2011 Cisco and/or its affiliates. All rights reserved.
16
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
16
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
© 2011 Cisco and/or its affiliates. All rights reserved.
17
IP-RAN
1 GE to Cellsite
-Cellsite (1GE)
-Access (10GE)
-Aggregation (40GE)
Ethernet –lease/build
uWave, Fiber media
Support 2G/3G/4G
IP/MPLS (L2/L3VPN)
Multicast capable
Traffic Offload
H-QoS
IPv6
Packet Core
10-100 GE enabled
POD architecture
Distributed Gateways
User policy & QoS
Bearer traffic
Traffic offload and
optimize
“SP security”
Optimize OTT
IPv6 on end-points
NAT44/64
MPLS Core
100GE enabled
BGP free, MPLS
enabled core
Scalable Routing
L3VPN as needed
Limited L2VPN
Traffic Engineering
Multi-exit Internet
6PE, 6VPE
National Datacenter
100GE enabled
Zones & POD
Control traffic
Virtualization
Storage
Cloud computing
will drive next-gen
M2M
communication
IMS Apps
IPv6
LTE ArchitectureFramework
Ethernet IP MPLS
Intelligence in Network
Virtualization Cloud Computing
17
IP-RAN
1 GE to Cellsite
-Cellsite (1GE)
-Access (10GE)
-Aggregation (40GE)
Ethernet –lease/build
uWave, Fiber media
Support 2G/3G/4G
IP/MPLS (L2/L3VPN)
Multicast capable
Traffic Offload
H-QoS
IPv6
Packet Core
10-100 GE enabled
POD architecture
Distributed Gateways
User policy & QoS
Bearer traffic
Traffic offload and
optimize
“SP security”
Optimize OTT
IPv6 on end-points
NAT44/64
MPLS Core
100GE enabled
BGP free, MPLS
enabled core
Scalable Routing
L3VPN as needed
Limited L2VPN
Traffic Engineering
Multi-exit Internet
6PE, 6VPE
National Datacenter
100GE enabled
Zones & POD
Control traffic
Virtualization
Storage
Cloud computing
will drive next-gen
M2M
communication
IMS Apps
IPv6
LTE ArchitectureFramework
Ethernet IP MPLS
Intelligence in Network
Virtualization Cloud Computing
© 2011 Cisco and/or its affiliates. All rights reserved.
18
IP/MPLS Core
Super Backbone
Regional Datacenter
Mobile gateways, WiFi Users-
P2P, Corp VPN
Apps -bearer, Billing, policy
Internet
Ent. Customer
(B2B, B2B2C, M2M
National Datacenter
Mobile User Apps hosted in NDC
Infra -Failover, Apps sharing, DCDR
Others -Cloud, hosting, contents
Partner Content-
hosted in SP network
Wireline Customer
(DSL, FTTH,ETTH)
Private Peering
Transit for Tier-2/3 ISP
Roaming Partners (IPSec VPN, 2G/3G,
LTE, Wi-Fi)
Partner (IPSec VPN)
Video Contents
Apps Development
Internet Peering
(Multiple locations)
IP-RAN Backhaul
(Any-to-any, L2/L3VPN,
RAN sharing, multicast)
Network Core Architecture
Simple, scalable, resilient architecture using optimal resources and support multiple
services on the same backbone infrastructure
RAN
2G/3G/4G, WiFi
18
IP/MPLS Core
Super Backbone
Regional Datacenter
Mobile gateways, WiFi Users-
P2P, Corp VPN
Apps -bearer, Billing, policy
Internet
Ent. Customer
(B2B, B2B2C, M2M
National Datacenter
Mobile User Apps hosted in NDC
Infra -Failover, Apps sharing, DCDR
Others -Cloud, hosting, contents
Partner Content-
hosted in SP network
Wireline Customer
(DSL, FTTH,ETTH)
Private Peering
Transit for Tier-2/3 ISP
Roaming Partners (IPSec VPN, 2G/3G,
LTE, Wi-Fi)
Partner (IPSec VPN)
Video Contents
Apps Development
Internet Peering
(Multiple locations)
IP-RAN Backhaul
(Any-to-any, L2/L3VPN,
RAN sharing, multicast)
Network Core Architecture
Simple, scalable, resilient architecture using optimal resources and support multiple
services on the same backbone infrastructure
RAN
2G/3G/4G, WiFi
© 2011 Cisco and/or its affiliates. All rights reserved.
19
Non-3GPP
IP Access
3GPP Access
3GPP
IP Access
Evolved Packet System
LTE/EPS Reference Architecture –10,000 Ft View
(Ref 3GPP TS23.401, TS23.402)
E-UTRAN
PDN
Gateway
Serving
Gateway
eNodeB
PCRF
Operator’s
IP Services
HSS
Gxc
(Gx+)
S11
(GTP-C)
S1-U
(GTP-U)
S2b
(PMIPv6,
GRE)
MME
S5 (PMIPv6, GRE)
S6a
(DIAMETER)
S1-MME
(S1-AP)
GERAN
S4 (GTP- C, GTP-U)
UTRAN
SGSN
Trusted
Non-
3GPP IP
Access
Untrusted
Non-
3GPP IP
Access
S3
(GTP-C)
S12 (GTP-U)
S10
(GTP-C)
S5 (GTP- C, GTP-U)
Gx
(Gx+)
Gxb
(Gx+)
SWx (DIAMETER)
STa (RADIUS,
DIAMETER)
ePDG
3GPP
AAA
SWn
(TBD)
S2c (DSMIPv6)
S2c
S6b
(DIAMETER)
SWm
(DIAMETER)
SGi
SWa
(TBD)
Gxa
(Gx+)
Rx+
S2c
UE
UE
UE
SWu (IKEv2,
MOBIKE, IPSec)
S2a
(PMIPv6, GRE
MIPv4 FACo A)
Trusted Untrusted
LTE
2G/3G
Transport (Tunneled Traffic)
IP Traffic
19
Non-3GPP
IP Access
3GPP Access
3GPP
IP Access
Evolved Packet System
LTE/EPS Reference Architecture –10,000 Ft View
(Ref 3GPP TS23.401, TS23.402)
E-UTRAN
PDN
Gateway
Serving
Gateway
eNodeB
PCRF
Operator’s
IP Services
HSS
Gxc
(Gx+)
S11
(GTP-C)
S1-U
(GTP-U)
S2b
(PMIPv6,
GRE)
MME
S5 (PMIPv6, GRE)
S6a
(DIAMETER)
S1-MME
(S1-AP)
GERAN
S4 (GTP- C, GTP-U)
UTRAN
SGSN
Trusted
Non-
3GPP IP
Access
Untrusted
Non-
3GPP IP
Access
S3
(GTP-C)
S12 (GTP-U)
S10
(GTP-C)
S5 (GTP- C, GTP-U)
Gx
(Gx+)
Gxb
(Gx+)
SWx (DIAMETER)
STa (RADIUS,
DIAMETER)
ePDG
3GPP
AAA
SWn
(TBD)
S2c (DSMIPv6)
S2c
S6b
(DIAMETER)
SWm
(DIAMETER)
SGi
SWa
(TBD)
Gxa
(Gx+)
Rx+
S2c
UE
UE
UE
SWu (IKEv2,
MOBIKE, IPSec)
S2a
(PMIPv6, GRE
MIPv4 FACo A)
Trusted Untrusted
LTE
2G/3G
Transport (Tunneled Traffic)
IP Traffic
© 2011 Cisco and/or its affiliates. All rights reserved.
20
Typical LTE/EPS Architecture –1,000 Ft View
EPC/SAEGateways
Mobility Adjuncts Elements
IMS Core
20
Typical LTE/EPS Architecture –1,000 Ft View
EPC/SAEGateways
Mobility Adjuncts Elements
IMS Core
© 2011 Cisco and/or its affiliates. All rights reserved.
21
Key LTE Requirements
•Ideal DL100Mb/s(5 bps/Hz), 3 -4 times Rel 6 HSDPA
•Ideal UL 50 Mb/s (2.5 bps/Hz, 2-3 times Rel 6 HSUPA
•Different MIMO configuration support
Throughput
•Radio Access Network latency < 10 ms,
•Control-Plane latency < 100 ms (R8), <50 ms ( R9)
•User-Plane latency <50 ms for real time Apps & voice
Strict QoS
•Mobility up to 350 km/h
•Roaming with 2/3G networks
•WiFi offload capability
Mobility
•Ability to delivery broadcast and multicast to mobiles
•Enhanced bit rate for MBMS
•Application registration directly by UE to Apps Server
Enhanced Multimedia
Broadcast Multicast
Service (eMBMS)
All-IP Architecture
•Any-to-any connectivity –L3VPN, L2VPN, TE
•Standard based interfaces
•SP security framework
21
Key LTE Requirements
•Ideal DL100Mb/s(5 bps/Hz), 3 -4 times Rel 6 HSDPA
•Ideal UL 50 Mb/s (2.5 bps/Hz, 2-3 times Rel 6 HSUPA
•Different MIMO configuration support
Throughput
•Radio Access Network latency < 10 ms,
•Control-Plane latency < 100 ms (R8), <50 ms ( R9)
•User-Plane latency <50 ms for real time Apps & voice
Strict QoS
•Mobility up to 350 km/h
•Roaming with 2/3G networks
•WiFi offload capability
Mobility
•Ability to delivery broadcast and multicast to mobiles
•Enhanced bit rate for MBMS
•Application registration directly by UE to Apps Server
Enhanced Multimedia
Broadcast Multicast
Service (eMBMS)
All-IP Architecture
•Any-to-any connectivity –L3VPN, L2VPN, TE
•Standard based interfaces
•SP security framework
© 2011 Cisco and/or its affiliates. All rights reserved.
22
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
22
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
© 2011 Cisco and/or its affiliates. All rights reserved.
23
Latency and delay components
Processing delay –depend on CPU, memory and load
Serialization delay-depend on packet size and interface speed
Queuing delay – depend upon packets in queue & serialization
Propagation delay –Depend on distance and media
Throughput is inversely proportional to roundtrip delay
How Does Latency, Packet Loss Impact LTE?
Illustration
23
Latency and delay components
Processing delay –depend on CPU, memory and load
Serialization delay-depend on packet size and interface speed
Queuing delay – depend upon packets in queue & serialization
Propagation delay –Depend on distance and media
Throughput is inversely proportional to roundtrip delay
How Does Latency, Packet Loss Impact LTE?
Illustration
© 2011 Cisco and/or its affiliates. All rights reserved.
24
Access Ring
uWave/ Fiber
Agg-1 Ring
MME/SGW/PGW
Apps (Bearer)
National Datacenter
HSS / PCRF/Billing
Apps (control)
AGG-1 AGG-2
AGG-3
CSN
IP BackhaulRadio
Radio Delay
IP Backhaul Transport Latency (Propagation & Processing)
Regional Datacenter (MME, SGW/PGW, DNS etc.) Processing Delays
MPLS Core Transport Latency (Propagation & Processing)
National Datacenter (HSS, PCRF, OCS, BM etc.) Processing Delays
Agg-2
Ring
Regional Datacenter
MPLS
Super backbone
Internet
Mobile Network and Latency Components
24
Access Ring
uWave/ Fiber
Agg-1 Ring
MME/SGW/PGW
Apps (Bearer)
National Datacenter
HSS / PCRF/Billing
Apps (control)
AGG-1 AGG-2
AGG-3
CSN
IP BackhaulRadio
Radio Delay
IP Backhaul Transport Latency (Propagation & Processing)
Regional Datacenter (MME, SGW/PGW, DNS etc.) Processing Delays
MPLS Core Transport Latency (Propagation & Processing)
National Datacenter (HSS, PCRF, OCS, BM etc.) Processing Delays
Agg-2
Ring
Regional Datacenter
MPLS
Super backbone
Internet
Mobile Network and Latency Components
© 2011 Cisco and/or its affiliates. All rights reserved.
25
Latency Requirements
Camped-state
(idle)
Active
(Cell_DCH)
Dormant
(Cell_PCH)
Less than 100msec
Less than 50msec
C-Plane Latency (ref TR25.913, V8.0.0) C-Plane Latency (ref TR36.913, V9.0.0)
Camped - state
Active
(in-sync)
Active – “dormant”
(un-sync)
Less than 50 ms
Less than 10 ms
•Idle to active < 100 ms when user plan is
established (excluding paging & NAS)
•Dormant to Active <50 ms
•Idle to active <50 ms when user plan is
established (excludes paging, NAS, S1
transfer)
•Dormant to Active <10 ms
Control Plane (C-Plane) –Relates to completion of RAN and CNsignaling
User Plan (U-Plane) –Relates to establishment of bearer path
25
Latency Requirements
Camped-state
(idle)
Active
(Cell_DCH)
Dormant
(Cell_PCH)
Less than 100msec
Less than 50msec
C-Plane Latency (ref TR25.913, V8.0.0) C-Plane Latency (ref TR36.913, V9.0.0)
Camped - state
Active
(in-sync)
Active – “dormant”
(un-sync)
Less than 50 ms
Less than 10 ms
•Idle to active < 100 ms when user plan is
established (excluding paging & NAS)
•Dormant to Active <50 ms
•Idle to active <50 ms when user plan is
established (excludes paging, NAS, S1
transfer)
•Dormant to Active <10 ms
Control Plane (C-Plane) –Relates to completion of RAN and CNsignaling
User Plan (U-Plane) –Relates to establishment of bearer path
© 2011 Cisco and/or its affiliates. All rights reserved.
26
UE eNB MME
5. RRC Connection Request
3. TA + Scheduling Grant
2. RACH Preamble
8. Connection Request
10. Connection Setup
12. RRC Connection Setup
15. RRC Connection Complete
9. Processing
delay in MME
1. Delay for RACH
Scheduling period
4. Processing delay
in UE
3. Processing delay
in eNB
7. Processing delay
in eNB
11. Processing
delay in eNB
14. Processing
delay in UE
13. H-ARQ Retransmission
16. H-ARQ Retransmission
6. H-ARQ Retransmission
RRC Contention Resolution
~1 ms
~4 ms
~2 ms
~4 ms
~1 ms
~1 ms
~4 ms
~7.5 ms ~15 ms
~7.5 ms
4 ms
~4 ms
~1 ms
~1 ms
~1 ms
~1 ms
~4 ms
C-Plane Latency (Idle to Active) -3GPP TS25.912
Total C-Plane = 47.5 ms + 2* S1-C transfer delay ~ 60 ms
Major components –Processing delays in UE, eNodeB, MME and Transport
26
UE eNB MME
5. RRC Connection Request
3. TA + Scheduling Grant
2. RACH Preamble
8. Connection Request
10. Connection Setup
12. RRC Connection Setup
15. RRC Connection Complete
9. Processing
delay in MME
1. Delay for RACH
Scheduling period
4. Processing delay
in UE
3. Processing delay
in eNB
7. Processing delay
in eNB
11. Processing
delay in eNB
14. Processing
delay in UE
13. H-ARQ Retransmission
16. H-ARQ Retransmission
6. H-ARQ Retransmission
RRC Contention Resolution
~1 ms
~4 ms
~2 ms
~4 ms
~1 ms
~1 ms
~4 ms
~7.5 ms ~15 ms
~7.5 ms
4 ms
~4 ms
~1 ms
~1 ms
~1 ms
~1 ms
~4 ms
C-Plane Latency (Idle to Active) -3GPP TS25.912
Total C-Plane = 47.5 ms + 2* S1-C transfer delay ~ 60 ms
Major components –Processing delays in UE, eNodeB, MME and Transport
© 2011 Cisco and/or its affiliates. All rights reserved.
27
UE eNodeB MME
2. Scheduling Request
4. Schedule grant
6. Transmit UL data
1ms
1ms
1ms
3. Processing3ms
5. Processing
1. Waiting1ms
5ms
UE is synced, so no need for NAS
C-Plane Latency (Dormant to Active) -(3GPP TS25.912)
27
UE eNodeB MME
2. Scheduling Request
4. Schedule grant
6. Transmit UL data
1ms
1ms
1ms
3. Processing3ms
5. Processing
1. Waiting1ms
5ms
UE is synced, so no need for NAS
C-Plane Latency (Dormant to Active) -(3GPP TS25.912)
© 2011 Cisco and/or its affiliates. All rights reserved.
28
U-Plane Latency-(3GPP TS25.912)
U-Plane Latency Refers to Establishment of Bearer Path to SGW
Description Duration
LTE_IDLELTE_ACTIVE delay (C-plane establishment) 47.5ms + 2 * Ts1c
TTIfor UL DATA PACKET 1ms
HARQRetransmission (@ 30%) 0.3 * 5ms
eNB Processing Delay (Uu–> S1-U) 1ms
U-plane establishment delay (RAN edge node) 51ms + 2 * Ts1c
S1-U Transfer delay Ts1u (1ms –15ms)
UPEProcessing delay (including context retrieval)10ms
U-plane establishment delay (Serving GW) 61ms+ 2 * Ts1c + Ts1u
Ts1c= 2ms–15 ms
Ts1u= 1ms – 15 ms
28
U-Plane Latency-(3GPP TS25.912)
U-Plane Latency Refers to Establishment of Bearer Path to SGW
Description Duration
LTE_IDLELTE_ACTIVE delay (C-plane establishment) 47.5ms + 2 * Ts1c
TTIfor UL DATA PACKET 1ms
HARQRetransmission (@ 30%) 0.3 * 5ms
eNB Processing Delay (Uu–> S1-U) 1ms
U-plane establishment delay (RAN edge node) 51ms + 2 * Ts1c
S1-U Transfer delay Ts1u (1ms –15ms)
UPEProcessing delay (including context retrieval)10ms
U-plane establishment delay (Serving GW) 61ms+ 2 * Ts1c + Ts1u
Ts1c= 2ms–15 ms
Ts1u= 1ms – 15 ms
© 2011 Cisco and/or its affiliates. All rights reserved.
29
QCI
Value
Resource
Type
PriorityDelay
Budget
(1)
Error Loss
Rate
(2)
Example Services
1
(3)
2 100ms 10
-2
Conversational Voice
2
(3)
GBR
4 150ms 10
-3
Conversational Video (Live Streaming)
3
(3)
3 50ms 10
-3
Real Time Gaming
4
(3)
5 300ms 10
-6
Non-Conversational Video (Buffered
Streaming)
5
(3)
1 100ms 10
-6
IMS Signalling
6
(4)
6 300ms 10
-6
Video (Buffered Streaming)
TCP-based (e.g., www, e- mail, chat, ftp, p2p
file sharing, progressive video, etc.)
7
(3)
Non-GBR 7 100ms
10
-3
Voice, Video (Live Streaming), Interactive
Gaming
8
(5)
8
300ms 10
-6
Video (Buffered Streaming)
TCP-based (e.g., www, e- mail, chat, ftp, p2p
sharing, progressive download,etc.)
9
(6)
9
Delay Budget for Applications- 3GPP TR23.401V8.1.0
29
QCI
Value
Resource
Type
PriorityDelay
Budget
(1)
Error Loss
Rate
(2)
Example Services
1
(3)
2 100ms 10
-2
Conversational Voice
2
(3)
GBR
4 150ms 10
-3
Conversational Video (Live Streaming)
3
(3)
3 50ms 10
-3
Real Time Gaming
4
(3)
5 300ms 10
-6
Non-Conversational Video (Buffered
Streaming)
5
(3)
1 100ms 10
-6
IMS Signalling
6
(4)
6 300ms 10
-6
Video (Buffered Streaming)
TCP-based (e.g., www, e- mail, chat, ftp, p2p
file sharing, progressive video, etc.)
7
(3)
Non-GBR 7 100ms
10
-3
Voice, Video (Live Streaming), Interactive
Gaming
8
(5)
8
300ms 10
-6
Video (Buffered Streaming)
TCP-based (e.g., www, e- mail, chat, ftp, p2p
sharing, progressive download,etc.)
9
(6)
9
Delay Budget for Applications- 3GPP TR23.401V8.1.0
© 2011 Cisco and/or its affiliates. All rights reserved.
30
Delay Budget for Default Bearer Establishment
Default bearer involve interaction of different entities
HSS, PCRF, APN-DNS are Apps and will have higher processing delays
Longer delay for default bearer will be perceived by user
Nodes Interface name Nodes Involved
Delay budget (Propagation,
processing ( ms)
eNB S1-MME/NAS eNodeB-MME ~50
MME S6a MME-HSS ~100
MME DNS MME-DNS (APN) ~50
MME S11 MME-SGW ~50
SGW S5/S8 SGW-PGW ~50
PGW Gx PGW-PCRF ~100
PGW Gy PGW-OCS ~100
Total bearer set-up time ~500
eNodeB X2 eNB-eNB 20
Delay budget measured in production environments
30
Delay Budget for Default Bearer Establishment
Default bearer involve interaction of different entities
HSS, PCRF, APN-DNS are Apps and will have higher processing delays
Longer delay for default bearer will be perceived by user
Nodes Interface name Nodes Involved
Delay budget (Propagation,
processing ( ms)
eNB S1-MME/NAS eNodeB-MME ~50
MME S6a MME-HSS ~100
MME DNS MME-DNS (APN) ~50
MME S11 MME-SGW ~50
SGW S5/S8 SGW-PGW ~50
PGW Gx PGW-PCRF ~100
PGW Gy PGW-OCS ~100
Total bearer set-up time ~500
eNodeB X2 eNB-eNB 20
Delay budget measured in production environments
© 2011 Cisco and/or its affiliates. All rights reserved.
31
First Person Shooter (FPS)
Need fast user response, interactive game
Latency –100 ms (E2E), jitter –10 ms, Packet loss –5%
Real Time Strategy (RTS)
Slightly relaxed with handful of players, slow response
Latency ~250 ms (E2E), jitter-50 ms, Packet loss –1%
Massive Multiplayer Online Role Playing Games (MMORPG)
Many players online, highly variable scenarios.
Delay budget –300 ms (E2E), Packet loss –5%
Non-Real Time Games (NRTG)
No strict criteria for latency e.g. chess
Delay budget –350 ms (E2E), Packet loss –5%
Real Time Gaming Requirements
Summary –Place interactive gaming Apps close to edge
31
First Person Shooter (FPS)
Need fast user response, interactive game
Latency –100 ms (E2E), jitter –10 ms, Packet loss –5%
Real Time Strategy (RTS)
Slightly relaxed with handful of players, slow response
Latency ~250 ms (E2E), jitter-50 ms, Packet loss –1%
Massive Multiplayer Online Role Playing Games (MMORPG)
Many players online, highly variable scenarios.
Delay budget –300 ms (E2E), Packet loss –5%
Non-Real Time Games (NRTG)
No strict criteria for latency e.g. chess
Delay budget –350 ms (E2E), Packet loss –5%
Real Time Gaming Requirements
Summary –Place interactive gaming Apps close to edge
© 2011 Cisco and/or its affiliates. All rights reserved.
32
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
32
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
© 2011 Cisco and/or its affiliates. All rights reserved.
33
Greenfield LTE deployments should be IPv6
Introduce dual stack LTE UE
Transport –Dual stack (Preference) or 6PE, 6VPE
All LTE Gateway interfaces should be IPv6
Internal Apps (i.e. IMS, Video etc.) should be IPv6
NAT64 for IPv4 internet
Deploying LTE in existing network
Introduce dual stack LTE UE
IPv6 for MME(S1-MME, S11), SGW(S1 -U, S5/S8), PGW(S5/ S8, SGi)
Transport –6PE, 6VPE to support LTE
Convert Internal Apps (i.e. IMS, Video etc.) to IPv6
Create Services islands-served by IPv4, IPv6
NAT64 for IPv4 internet
Integrate with existing 2.5/3G network on IPv4
IPv6 Planning Design Considerations
33
Greenfield LTE deployments should be IPv6
Introduce dual stack LTE UE
Transport –Dual stack (Preference) or 6PE, 6VPE
All LTE Gateway interfaces should be IPv6
Internal Apps (i.e. IMS, Video etc.) should be IPv6
NAT64 for IPv4 internet
Deploying LTE in existing network
Introduce dual stack LTE UE
IPv6 for MME(S1-MME, S11), SGW(S1 -U, S5/S8), PGW(S5/ S8, SGi)
Transport –6PE, 6VPE to support LTE
Convert Internal Apps (i.e. IMS, Video etc.) to IPv6
Create Services islands-served by IPv4, IPv6
NAT64 for IPv4 internet
Integrate with existing 2.5/3G network on IPv4
IPv6 Planning Design Considerations
© 2011 Cisco and/or its affiliates. All rights reserved.
34
Interface ID
/32 /64/16
128 Bits
/48
Regions (/40 256 regions)
Functions within region (/48 provides 256 functions)
(eNodeB, IP-BH, MPLS Core, MME, HSS, SGW, PGW,
Datacenter, Security etc.)
Devices and subnets for each devices
(48 –64 provides 65,000 subnet of /64)
IPv6 Subnet Considerations for Infrastructure
Infrastructure subnets are typically notannounced to internet
Summarization –optimize routing and easy to scale
Point-to-point Interface address: Choices -/127, /64
Loopback /128
Subnetting Example (Assuming - /32 for Infrastructure)
34
Interface ID
/32 /64/16
128 Bits
/48
Regions (/40 256 regions)
Functions within region (/48 provides 256 functions)
(eNodeB, IP-BH, MPLS Core, MME, HSS, SGW, PGW,
Datacenter, Security etc.)
Devices and subnets for each devices
(48 –64 provides 65,000 subnet of /64)
IPv6 Subnet Considerations for Infrastructure
Infrastructure subnets are typically notannounced to internet
Summarization –optimize routing and easy to scale
Point-to-point Interface address: Choices -/127, /64
Loopback /128
Subnetting Example (Assuming - /32 for Infrastructure)
© 2011 Cisco and/or its affiliates. All rights reserved.
35
Interface ID
/32 /64/16
128 Bits
/48
Regions (/40 256 regions)
Services/APN within region (/48 provides 256 )
(IMS, Internet, Video, M2M, Message, Enterprise etc.)
Devices and subnets for each devices **
(48 –64 provides 65K users within each service/APN)
IPv6 Subnet Considerations for Subscribers
LTE Users IPv6 subnets are announced to internet
Separate block for each service i.e. APN/virtual APN
Allocation strategy – Local Pool, AAA, DHCPv6
Subnet strategy –Ability to identify services, easy growth
Subnetting Example (Assuming /32 for LTE Users)
** For wireless routers gateway allocated smaller block i.e. /60, /56 or /48 etc.
35
Interface ID
/32 /64/16
128 Bits
/48
Regions (/40 256 regions)
Services/APN within region (/48 provides 256 )
(IMS, Internet, Video, M2M, Message, Enterprise etc.)
Devices and subnets for each devices **
(48 –64 provides 65K users within each service/APN)
IPv6 Subnet Considerations for Subscribers
LTE Users IPv6 subnets are announced to internet
Separate block for each service i.e. APN/virtual APN
Allocation strategy – Local Pool, AAA, DHCPv6
Subnet strategy –Ability to identify services, easy growth
Subnetting Example (Assuming /32 for LTE Users)
** For wireless routers gateway allocated smaller block i.e. /60, /56 or /48 etc.
© 2011 Cisco and/or its affiliates. All rights reserved.
36
Transport Traffic –Control
Provide user authentication, establish data sessions
Network Layer -IPv4, Dual stack or native IPv6
Transport -Radio Access Network & Mobile Backhaul
36
Transport Traffic –Control
Provide user authentication, establish data sessions
Network Layer -IPv4, Dual stack or native IPv6
Transport -Radio Access Network & Mobile Backhaul
© 2011 Cisco and/or its affiliates. All rights reserved.
37
Transport Traffic -Bearer
Two way user traffic between Usersand Applications
Encapsulated in tunnel (GTP)
Default Bearer and Dedicated Bearer(s) if Required
Service Level QoS
37
Transport Traffic -Bearer
Two way user traffic between Usersand Applications
Encapsulated in tunnel (GTP)
Default Bearer and Dedicated Bearer(s) if Required
Service Level QoS
© 2011 Cisco and/or its affiliates. All rights reserved.
38
3GPP Rel-8 onward
Dual stack User send one PDP request “IPv4v6”
Gateway will create bearer; Allocate IPv4 & IPv6 to same bearer
For GPRS network single bearer is applicable from 3GPP Rel-9 onward
Prior to 3GPP Rel-8 (LTE introduced from Rel-8 onward)
Dual-stack User sends two PDP requests-One of for IPv4 and another for IPv6
Gateway creates two unique PDP-contexts-One for IPv4 and another for IPv6.
Transport Traffic - Bearer Setup for Subscriber
Dual stack
Dual stack
38
3GPP Rel-8 onward
Dual stack User send one PDP request “IPv4v6”
Gateway will create bearer; Allocate IPv4 & IPv6 to same bearer
For GPRS network single bearer is applicable from 3GPP Rel-9 onward
Prior to 3GPP Rel-8 (LTE introduced from Rel-8 onward)
Dual-stack User sends two PDP requests-One of for IPv4 and another for IPv6
Gateway creates two unique PDP-contexts-One for IPv4 and another for IPv6.
Transport Traffic - Bearer Setup for Subscriber
Dual stack
Dual stack
© 2011 Cisco and/or its affiliates. All rights reserved.
39
Subscriber IPv6 Address Allocation
Create Session Request
(APN, QoS,
PDN-type=IPv6,…)
Create Session Request
(APN, QoS,
PDN-type=IPv6,…)
Create Session Reply
(UE Prefix,
Protocol config options
(e.g. DNS-server list,…),
cause)
Create Session Reply
(UE Prefix,
Protocol config options,
cause)
AAA DHCPPGWSGWMME
Attach Request
Attach Accept
Router Solicitation
Router Advertisement
UE
DHCPv6 –Information Request
DHCPv6 PD
Option 3
DHCPv6 –Confirm
DHCPv6 –Relay Forward
DHCPv6 –confirm
DHCPv6 –Reply forward DHCPv6 –Relay Reply
Prefix Retrieval
Option 2
Option 1/64 prefix allocation from local pool
SLAAC
Prefix communicated to
SGW/MME
empty UE IP-address
for dynamic allocation
/64 prefix allocation:
3 Options: Local Pool, AAA, DHCP
UE ignore IPv6 pref ix
received in attach
MME compare requested PDP types (IPv4, IPv6, IPv4v6) with HSS
RA contain the same IPv6 pref ix as the one provided during def ault bearer establishment
UE request additional inf ormation in DHCPv6
39
Subscriber IPv6 Address Allocation
Create Session Request
(APN, QoS,
PDN-type=IPv6,…)
Create Session Request
(APN, QoS,
PDN-type=IPv6,…)
Create Session Reply
(UE Prefix,
Protocol config options
(e.g. DNS-server list,…),
cause)
Create Session Reply
(UE Prefix,
Protocol config options,
cause)
AAA DHCPPGWSGWMME
Attach Request
Attach Accept
Router Solicitation
Router Advertisement
UE
DHCPv6 –Information Request
DHCPv6 PD
Option 3
DHCPv6 –Confirm
DHCPv6 –Relay Forward
DHCPv6 –confirm
DHCPv6 –Reply forward DHCPv6 –Relay Reply
Prefix Retrieval
Option 2
Option 1/64 prefix allocation from local pool
SLAAC
Prefix communicated to
SGW/MME
empty UE IP-address
for dynamic allocation
/64 prefix allocation:
3 Options: Local Pool, AAA, DHCP
UE ignore IPv6 pref ix
received in attach
MME compare requested PDP types (IPv4, IPv6, IPv4v6) with HSS
RA contain the same IPv6 pref ix as the one provided during def ault bearer establishment
UE request additional inf ormation in DHCPv6
© 2011 Cisco and/or its affiliates. All rights reserved.
40
Mobile Router (3GPP Rel-10)
/64
/64
/64
Connection-Prefix: /64
UE…
Delegation of “/60 minus
connection-prefix”
UE represented by single prefix (here “/60”)
-in routing and OSS/ PCCsystems
Enable LTE UE to work as Mobile router (/60) & Each client get /64
Prefix Delegation w/ DHCPv6 PD (RFC3633) on top of existing address
LTE UE request DHCPv6 Prefix delegation
DHCPv6 allocate prefix (e.g. /60) “prefix minus connection-prefix”
delegated using Prefix-Exclude option (see draft -korhonen-dhc
-pd-
exclude)
LTE UE further allocate /64 to clients minus connection-prefix
FUTURE
40
Mobile Router (3GPP Rel-10)
/64
/64
/64
Connection-Prefix: /64
UE…
Delegation of “/60 minus
connection-prefix”
UE represented by single prefix (here “/60”)
-in routing and OSS/ PCCsystems
Enable LTE UE to work as Mobile router (/60) & Each client get /64
Prefix Delegation w/ DHCPv6 PD (RFC3633) on top of existing address
LTE UE request DHCPv6 Prefix delegation
DHCPv6 allocate prefix (e.g. /60) “prefix minus connection-prefix”
delegated using Prefix-Exclude option (see draft -korhonen-dhc
-pd-
exclude)
LTE UE further allocate /64 to clients minus connection-prefix
FUTURE
© 2011 Cisco and/or its affiliates. All rights reserved.
41
IPv6 Prefix Delegation in 3GPP Network
3GPP TS 23.060 & 23.401 (Rel-10)
Create Session Request
(APN, QoS, PDN-type=IPv6,…)
Create Session Request
(APN, QoS, PDN-type=IPv6,…)
Create Session Reply
(UE IP-address,
Protocol config options (e.g.
DNS-server list,…), cause)
Create Session Reply
(UE IP-address,
Protocol config options, cause)
AAA
Authentication & Config
DHCPPGWSGWMME
Attach Request
Attach Accept
Router Solicitation
Router Advertisement
empty UE IP-address for
dynamic allocation
UE
(Requesting Router) (Delegating Router)
DHCPv6 –Solict ( IA_PD (1+) OPTION_PD_EXCLUDE, [RAPID_COMMIT] )
DHCPv6 –Advertize (
IA_PD Prefix (1+) OPTION_PD_EXCLUDE )
DHCPv6 –Request (
IA_PD Prefix (1+) OPTION_PD_EXCLUDE )
DHCPv6 –Reply (
IA_PD Prefix (1+) OPTION_PD_EXCLUDE )
PD Prefix(es) is/are obtained
SLAAC
In-Home
Network 1
In-Home
Network 1
Authentication
DHCPv6 Config
Option 1
Option 2
IPv6 Address assignment for
end hosts (using SLAAC or
DHCPv6)
DHCPv6 Prefix Delegation
Single Prefix allocated
Prefix communicated to SGW/MME
FUTURE
41
IPv6 Prefix Delegation in 3GPP Network
3GPP TS 23.060 & 23.401 (Rel-10)
Create Session Request
(APN, QoS, PDN-type=IPv6,…)
Create Session Request
(APN, QoS, PDN-type=IPv6,…)
Create Session Reply
(UE IP-address,
Protocol config options (e.g.
DNS-server list,…), cause)
Create Session Reply
(UE IP-address,
Protocol config options, cause)
AAA
Authentication & Config
DHCPPGWSGWMME
Attach Request
Attach Accept
Router Solicitation
Router Advertisement
empty UE IP-address for
dynamic allocation
UE
(Requesting Router) (Delegating Router)
DHCPv6 –Solict ( IA_PD (1+) OPTION_PD_EXCLUDE, [RAPID_COMMIT] )
DHCPv6 –Advertize (
IA_PD Prefix (1+) OPTION_PD_EXCLUDE )
DHCPv6 –Request (
IA_PD Prefix (1+) OPTION_PD_EXCLUDE )
DHCPv6 –Reply (
IA_PD Prefix (1+) OPTION_PD_EXCLUDE )
PD Prefix(es) is/are obtained
SLAAC
In-Home
Network 1
In-Home
Network 1
Authentication
DHCPv6 Config
Option 1
Option 2
IPv6 Address assignment for
end hosts (using SLAAC or
DHCPv6)
DHCPv6 Prefix Delegation
Single Prefix allocated
Prefix communicated to SGW/MME
FUTURE
© 2011 Cisco and/or its affiliates. All rights reserved.
42
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
42
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
© 2011 Cisco and/or its affiliates. All rights reserved.
43
Distributed
MME+SGSN
+GGSN
+SGW+PGW
Distributed
MME+SGSN
+GGSN
+SGW+PGW
Distributed
MME+SGSN
Distributed
MME+SGSN
Centralized
SGW+PGW
+GGSN
Distributed
MME+SGSN
+GGSN
SGW+PGW
IP Backbone
LTE
2.5G
3G
Centralized
SGSN+GGSN
MME+SGW+PGW
IP Backbone
LTE
2.5G
3G
IP Backbone
LTE
2.5G
3G
Distributed
SGW+PGW+GGSN
Distributed
SGW+PGW+GGSN
Centralized
MME+SGSN
IP Backbone
LTE
2.5G
3G
Design Considerations
Deciding which Combo Nodes?
43
Distributed
MME+SGSN
+GGSN
+SGW+PGW
Distributed
MME+SGSN
+GGSN
+SGW+PGW
Distributed
MME+SGSN
Distributed
MME+SGSN
Centralized
SGW+PGW
+GGSN
Distributed
MME+SGSN
+GGSN
SGW+PGW
IP Backbone
LTE
2.5G
3G
Centralized
SGSN+GGSN
MME+SGW+PGW
IP Backbone
LTE
2.5G
3G
IP Backbone
LTE
2.5G
3G
Distributed
SGW+PGW+GGSN
Distributed
SGW+PGW+GGSN
Centralized
MME+SGSN
IP Backbone
LTE
2.5G
3G
Design Considerations
Deciding which Combo Nodes?
© 2011 Cisco and/or its affiliates. All rights reserved.
44
Recommendation LTE/EPC Gateways Location
Entity PlacementConsiderations
MME Moderatedistribution
•Latency <50ms from eNB to MME (S1-MME),
•Faster signaling/call setup
•Use MME pooling -scaling & geographical redundancy
SGW/PGW Distributed, close to edge
•Ability to serve video locally
•Latency <50 ms from eNB (S1-U), better user experience
•Co-locate/Co-host SGW/PGW if design permit
•Mobile Service Edge gateway (MSEG) might be an option to offload
usertraffic, closer to edge
HSS Centralized/Moderate distribution
•Latency <100 ms. Latency impact default bearer set-up
•Partition HSS as front end and backend if design permit
•Front-endco-locate with MME if possible
SPR/DBE Centralized
•Latency <100 ms. Latency impact database query, sync
•Replicate database at multiple locations
•Co-locate with HSS backend
44
Recommendation LTE/EPC Gateways Location
Entity PlacementConsiderations
MME Moderatedistribution
•Latency <50ms from eNB to MME (S1-MME),
•Faster signaling/call setup
•Use MME pooling -scaling & geographical redundancy
SGW/PGW Distributed, close to edge
•Ability to serve video locally
•Latency <50 ms from eNB (S1-U), better user experience
•Co-locate/Co-host SGW/PGW if design permit
•Mobile Service Edge gateway (MSEG) might be an option to offload
usertraffic, closer to edge
HSS Centralized/Moderate distribution
•Latency <100 ms. Latency impact default bearer set-up
•Partition HSS as front end and backend if design permit
•Front-endco-locate with MME if possible
SPR/DBE Centralized
•Latency <100 ms. Latency impact database query, sync
•Replicate database at multiple locations
•Co-locate with HSS backend
© 2011 Cisco and/or its affiliates. All rights reserved.
45
Recommendation LTE/EPC Gateways Location
Entity PlacementConsiderations
PCRF,
Balance
Manager,
Online
Charging
System
Centralized
•Latency <100 ms. Latency impact policy download, updates
•Can share database with HSS
•Balance Manager, Online Charging co-located with PCRF
DNS •Tracking Area/APN DNS –Used by MME, Centralized
•Mobile DNS –Used by UE, distributed. Co-located with PGW
•InternetDNS –Used for inbound query, Centralized
•Roam DNS – Used by roaming partners, Centralized
•Infrastructure DNS –Used by internal infrastructures, Centralized
AAA Centralized
•Used for ePDG (3GPP) – centralized
•Infra. device authentication -centralized
DHCP Centralized
•DHCPv6for IP address allocation
45
Recommendation LTE/EPC Gateways Location
Entity PlacementConsiderations
PCRF,
Balance
Manager,
Online
Charging
System
Centralized
•Latency <100 ms. Latency impact policy download, updates
•Can share database with HSS
•Balance Manager, Online Charging co-located with PCRF
DNS •Tracking Area/APN DNS –Used by MME, Centralized
•Mobile DNS –Used by UE, distributed. Co-located with PGW
•InternetDNS –Used for inbound query, Centralized
•Roam DNS – Used by roaming partners, Centralized
•Infrastructure DNS –Used by internal infrastructures, Centralized
AAA Centralized
•Used for ePDG (3GPP) – centralized
•Infra. device authentication -centralized
DHCP Centralized
•DHCPv6for IP address allocation
© 2011 Cisco and/or its affiliates. All rights reserved.
46
MME Design Parameters
MMEparameters Per sub/Hr Typical values**
1
InitialUEAttach/Detach
2Bearer activation/deactivation per PDN session
3PDN connection setup/tear down
4Ingress paging
5Egress paging
6Idle-active/active-idle transactions
7Number of bearer perPDN session
8Number of PDN sessions
9Intra-MMES1 handoverwith SGW relocation
10Intra-MMES1 handover withoutSGW relocation
11Intra-MME X2handover
12Inter-MME handover
13Intra-MME tracking area updates
14Inter-MME tracking area updates
MME Handle Control Plane Signaling Toward eNB, HSS, SGSN, SGW etc.
46
MME Design Parameters
MMEparameters Per sub/Hr Typical values**
1
InitialUEAttach/Detach
2Bearer activation/deactivation per PDN session
3PDN connection setup/tear down
4Ingress paging
5Egress paging
6Idle-active/active-idle transactions
7Number of bearer perPDN session
8Number of PDN sessions
9Intra-MMES1 handoverwith SGW relocation
10Intra-MMES1 handover withoutSGW relocation
11Intra-MME X2handover
12Inter-MME handover
13Intra-MME tracking area updates
14Inter-MME tracking area updates
MME Handle Control Plane Signaling Toward eNB, HSS, SGSN, SGW etc.
© 2011 Cisco and/or its affiliates. All rights reserved.
47
What is MME Pooling?
Region B
MME POOL
MME A
MME
C
Region A
MME B
Region C
Number of MME’s clustered in pool across geographical area
MME is identified by Code & Group Identifier
All MME in pool will have same Group identifier
47
What is MME Pooling?
Region B
MME POOL
MME A
MME
C
Region A
MME B
Region C
Number of MME’s clustered in pool across geographical area
MME is identified by Code & Group Identifier
All MME in pool will have same Group identifier
© 2011 Cisco and/or its affiliates. All rights reserved.
48
Benefits of MME Pooling
Enables geographical redundancy, as a pool can be
distributed across sites.
Increases overall capacity, as load sharing across the
MMEsin a pool is possible.
Converts inter-MME Tracking Area Updates (TAUs) to
intra-MME TAUsfor moves between the MMEs of the
same pool. This substantially reduces signaling load as
well as data transfer delays.
Eases introduction of new nodes and replacement of old
nodes as subscribers can be moved is a planned manner
to the new node.
Eliminates single point of failure between an eNodeB
and MME.
Enables service downtime free maintenance
scheduling.
48
Benefits of MME Pooling
Enables geographical redundancy, as a pool can be
distributed across sites.
Increases overall capacity, as load sharing across the
MMEsin a pool is possible.
Converts inter-MME Tracking Area Updates (TAUs) to
intra-MME TAUsfor moves between the MMEs of the
same pool. This substantially reduces signaling load as
well as data transfer delays.
Eases introduction of new nodes and replacement of old
nodes as subscribers can be moved is a planned manner
to the new node.
Eliminates single point of failure between an eNodeB
and MME.
Enables service downtime free maintenance
scheduling.
© 2011 Cisco and/or its affiliates. All rights reserved.
49
MME Paging Considerations
Signaling Storm –High Paging
Idle mode paging causes volumes of signaling traffic
Impacts radio network where paging is a common resource
Ideally SGW do not discriminate among received packets
Any packet is page eligible
Signaling storms & drain mobile battery
In worst case, it may be an attack to bring the network down
May not be able to bill for delivery of unwanted packets
Vulnerable to DoSand DDoSattacks
Need to qualify DL packets before page request initiation
Solution
MME maintain list of mobile & eNB from which last registered
Page selected eNB
No response then page all eNB in Tracking Area ID
Use selective & Application aware paging
49
MME Paging Considerations
Signaling Storm –High Paging
Idle mode paging causes volumes of signaling traffic
Impacts radio network where paging is a common resource
Ideally SGW do not discriminate among received packets
Any packet is page eligible
Signaling storms & drain mobile battery
In worst case, it may be an attack to bring the network down
May not be able to bill for delivery of unwanted packets
Vulnerable to DoSand DDoSattacks
Need to qualify DL packets before page request initiation
Solution
MME maintain list of mobile & eNB from which last registered
Page selected eNB
No response then page all eNB in Tracking Area ID
Use selective & Application aware paging
© 2011 Cisco and/or its affiliates. All rights reserved.
50
SGW/PGW Parameters Typical values**
1Numberof Simultaneous active subs
2Numberof subs using IPv4 (% IPv4 PDN)
3Numberof subs using IPv6 (% IPv6 PDN)
4Number of subs using IPv4v6 (% IPv4v6 PDN)
5Number of bearer activation/deactivation per PDN/Hr
6Number of average bearer per PDN connection
7Numberof PDN connection setup/tear down per sub/Hr
8Number of PDN session per sub
9Number of idle-active/active-idle transaction per sub/Hr
10Number of intraSGW handover per sub/Hr
11Number of InterSGW handover per sub/Hr
12Number of inter-system handover persub/Hr
SGW handle control & bearer, whereas PGW mainly handle bearer traffic
SGW/PGW combo balance control & bearer traffic
SGW/PGW Design Parameters
50
SGW/PGW Parameters Typical values**
1Numberof Simultaneous active subs
2Numberof subs using IPv4 (% IPv4 PDN)
3Numberof subs using IPv6 (% IPv6 PDN)
4Number of subs using IPv4v6 (% IPv4v6 PDN)
5Number of bearer activation/deactivation per PDN/Hr
6Number of average bearer per PDN connection
7Numberof PDN connection setup/tear down per sub/Hr
8Number of PDN session per sub
9Number of idle-active/active-idle transaction per sub/Hr
10Number of intraSGW handover per sub/Hr
11Number of InterSGW handover per sub/Hr
12Number of inter-system handover persub/Hr
SGW handle control & bearer, whereas PGW mainly handle bearer traffic
SGW/PGW combo balance control & bearer traffic
SGW/PGW Design Parameters
© 2011 Cisco and/or its affiliates. All rights reserved.
51
SGW/PGW Parameters Typical
values**
PCEF (PolicyControl Enforcement Function) Design
1 No of flow /subscriber
2 % of deepflow inspection
3 % of deep packet inspection
4 % ofPDN connection using Gy (pre-paid)
5 % ofPDN connection using Gx (Policy interface)
6 Number of Gx Transactions per PDN Connection/Hr
6 Number of Dynamic Rules
DataSubs Traffic
1 %of subs simultaneously sending/receiving data
2 Average packet size for DL
3 Average packet sizefor UL
SGW/PGW Design Parameters (Cont’d)
51
SGW/PGW Parameters Typical
values**
PCEF (PolicyControl Enforcement Function) Design
1 No of flow /subscriber
2 % of deepflow inspection
3 % of deep packet inspection
4 % ofPDN connection using Gy (pre-paid)
5 % ofPDN connection using Gx (Policy interface)
6 Number of Gx Transactions per PDN Connection/Hr
6 Number of Dynamic Rules
DataSubs Traffic
1 %of subs simultaneously sending/receiving data
2 Average packet size for DL
3 Average packet sizefor UL
SGW/PGW Design Parameters (Cont’d)
© 2011 Cisco and/or its affiliates. All rights reserved.
52
What is SGW Serving Area?
Like MME; SGW’s can also clustered as “serving area”
MME has greater option to select SGW
Reduce signaling overhead –inter SGW handover
eNB have S1Ulink to multiple SGW in pool
LTE UE is bear S1Uonly to one SGW
Each SGW serving area has one Tracking Area Identifier (TAI)
52
What is SGW Serving Area?
Like MME; SGW’s can also clustered as “serving area”
MME has greater option to select SGW
Reduce signaling overhead –inter SGW handover
eNB have S1Ulink to multiple SGW in pool
LTE UE is bear S1Uonly to one SGW
Each SGW serving area has one Tracking Area Identifier (TAI)
© 2011 Cisco and/or its affiliates. All rights reserved.
53
DNS Design
DNS Functional description
Tracking Area/APN
DNS
Initial Attach
•MME perform APN query to find PGW, MME perform track Area query to find SGW
Handover with TAI change & Tracking Area Updates
•MME perform track query to determine SGW
•MME select closest SGW to PGW send create session request
Mobile DNS •LTE UE query mobile DNS to resolve “Host Name” to IP address
•Can be DNS64 (LTE UE with IPv6), DNS44(LTE UE with IPv4)
Internet DNS •Mainly root DNS. Need DNS64 capability
Infrastructure DNS•Name resolution in the OAM (e.g. admin to login to the device, SNMP)
Roam DNS •Used for roaming traffic. Need IPv6 capability of roaming transport is IPv6
E-UTRAN
PDN
Gateway
Serving
Gateway
eNodeB
PCRF
Operator’s
IP Services
HSS
Gxc
(Gx+)
S11
(GTP-C)
S1-U (GTP-U)
MME
S6a
(DIAMETER)
S1-MME
(S1-AP)
S5(GTP-C,GTP -U)
Gx
(Gx+)
SWx (DIAMETER)
3GPP
AAAS6b
(DIAMETER)
SGi
Rx+
UE
Tracking Area/APN DNS
Mobile DNS
S10 (GTP-C
Infrastructure DNS
Internet DNS
Roam DNS
53
DNS Design
DNS Functional description
Tracking Area/APN
DNS
Initial Attach
•MME perform APN query to find PGW, MME perform track Area query to find SGW
Handover with TAI change & Tracking Area Updates
•MME perform track query to determine SGW
•MME select closest SGW to PGW send create session request
Mobile DNS •LTE UE query mobile DNS to resolve “Host Name” to IP address
•Can be DNS64 (LTE UE with IPv6), DNS44(LTE UE with IPv4)
Internet DNS •Mainly root DNS. Need DNS64 capability
Infrastructure DNS•Name resolution in the OAM (e.g. admin to login to the device, SNMP)
Roam DNS •Used for roaming traffic. Need IPv6 capability of roaming transport is IPv6
E-UTRAN
PDN
Gateway
Serving
Gateway
eNodeB
PCRF
Operator’s
IP Services
HSS
Gxc
(Gx+)
S11
(GTP-C)
S1-U (GTP-U)
MME
S6a
(DIAMETER)
S1-MME
(S1-AP)
S5(GTP-C,GTP -U)
Gx
(Gx+)
SWx (DIAMETER)
3GPP
AAAS6b
(DIAMETER)
SGi
Rx+
UE
Tracking Area/APN DNS
Mobile DNS
S10 (GTP-C
Infrastructure DNS
Internet DNS
Roam DNS
© 2011 Cisco and/or its affiliates. All rights reserved.
54
DNS64 Traffic Flow
54
DNS64 Traffic Flow
© 2011 Cisco and/or its affiliates. All rights reserved.
55
Large Scale NAT - Where to Place the NAT
Function?
PGWeNB
IPv4
private IPv4
IPv4
Public
public IPv4
SGW
NAT44/64
PGWeNB
IPv4 IPv4
private IPv4 private IPv4
IPv4
Public
public IPv4
CGN/
CGv6
SGW
N AT
NAT44/64
N AT
Option 1: NAT on Mobile Gateway (Distributed)
Option 2: NAT on Router (Centralized)
Key Benefits:
•Subscriber aware NAT
-per subscriber control
-per subscriber accounting
•Large Scale (further
enhanced by distribution)
•Highly available
(incl. geo- redundancy)
Key Benefits:
•Integrated NAT for multiple
administrative domains
(operational separation)
•Large Scale
•Overlapping private IPv4
domains (e.g. w/ VPNs)
•Intelligent routing to LSN
55
Large Scale NAT - Where to Place the NAT
Function?
PGWeNB
IPv4
private IPv4
IPv4
Public
public IPv4
SGW
NAT44/64
PGWeNB
IPv4 IPv4
private IPv4 private IPv4
IPv4
Public
public IPv4
CGN/
CGv6
SGW
N AT
NAT44/64
N AT
Option 1: NAT on Mobile Gateway (Distributed)
Option 2: NAT on Router (Centralized)
Key Benefits:
•Subscriber aware NAT
-per subscriber control
-per subscriber accounting
•Large Scale (further
enhanced by distribution)
•Highly available
(incl. geo- redundancy)
Key Benefits:
•Integrated NAT for multiple
administrative domains
(operational separation)
•Large Scale
•Overlapping private IPv4
domains (e.g. w/ VPNs)
•Intelligent routing to LSN
© 2011 Cisco and/or its affiliates. All rights reserved.
56
Routing to Multiple CGN Gateways
CGN announce their availability with dynamic state
Mobile Gateway select the best route and forward traffic
Internet
CGN2
CGN1
Mobile gateway
PGW
User
1
2
Service.Transport-Attachment: “VPN Blue”, CGN1
Service.Type: NAT64 or NAT44
Service.Load.Bandwidth.Available: 10 Gbps
Service.Load.Bandwidth.10min- average: 2.3 Gbps
Service.Load.Bindings.Available: 2.000.000
Service.Load.Bindings.10- min-average: 500.000
Service.Transport-Attachment: “VPN-Blue”, CGN2
Service.Type: NAT64 or NAT44
Service.Load.Bandwidth.Available: 10 Gbps
Service.Load.Bandwidth.10min- average: 5 Gbps
Service.Load.Bindings.Available: 3.000.000
Service.Load.Bindings.10- min-average: 500.000
FUTURE
56
Routing to Multiple CGN Gateways
CGN announce their availability with dynamic state
Mobile Gateway select the best route and forward traffic
Internet
CGN2
CGN1
Mobile gateway
PGW
User
1
2
Service.Transport-Attachment: “VPN Blue”, CGN1
Service.Type: NAT64 or NAT44
Service.Load.Bandwidth.Available: 10 Gbps
Service.Load.Bandwidth.10min- average: 2.3 Gbps
Service.Load.Bindings.Available: 2.000.000
Service.Load.Bindings.10- min-average: 500.000
Service.Transport-Attachment: “VPN-Blue”, CGN2
Service.Type: NAT64 or NAT44
Service.Load.Bandwidth.Available: 10 Gbps
Service.Load.Bandwidth.10min- average: 5 Gbps
Service.Load.Bindings.Available: 3.000.000
Service.Load.Bindings.10- min-average: 500.000
FUTURE
© 2011 Cisco and/or its affiliates. All rights reserved.
57
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning –Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
57
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning –Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
© 2011 Cisco and/or its affiliates. All rights reserved.
58
Transport Planning –Mobile Backhaul, Core
UE traffic
served by eNodeBs
Last mile
serves eNodeBs
aggregation
core
eNodeBs
Transport
network
External
Networks
Mobile Backhaul – Access
Bandwidth- Full access capacity (Peak rate)
Resiliency, failover, dual homing
Routing -L2/L3based on requirements.
L3is recommended
Core/Super backbone
Bandwidth -mean average with over
subscription
Connecting backhaul from all regions
Regional and National Datacenter
Internet, roaming partners, Applications
Routing –MPLS VPN/Global routing
Mobile Backhaul – Pre-agg/Agg
Bandwidth- mean average with oversubscription
Aggregating access and pre-agg rings
Agile & resilient architecture to backhaul BW
Routing- L2/L3VPN, Any-to-any routing
58
Transport Planning –Mobile Backhaul, Core
UE traffic
served by eNodeBs
Last mile
serves eNodeBs
aggregation
core
eNodeBs
Transport
network
External
Networks
Mobile Backhaul – Access
Bandwidth- Full access capacity (Peak rate)
Resiliency, failover, dual homing
Routing -L2/L3based on requirements.
L3is recommended
Core/Super backbone
Bandwidth -mean average with over
subscription
Connecting backhaul from all regions
Regional and National Datacenter
Internet, roaming partners, Applications
Routing –MPLS VPN/Global routing
Mobile Backhaul – Pre-agg/Agg
Bandwidth- mean average with oversubscription
Aggregating access and pre-agg rings
Agile & resilient architecture to backhaul BW
Routing- L2/L3VPN, Any-to-any routing
© 2011 Cisco and/or its affiliates. All rights reserved.
59
* NGMN- Next Generation Mobile Network (Alliance of Mobile service Providers)
Mobile Backhaul Design Requirements
NGMNAlliance has released about 91 Requirements*
eNB –Multi-homing to MME/SGW (S1-Flex), RAN sharing
Max 16 S1 interfaces, 6 operators (S1-Flex)
Multicast Capability (eMBMS)
QoS -QCI to DSCP/CoSmapping, Shape, Rate limit
Bandwidth-LTE radio, other traffic (enterprise, WiFi)
BW optimization, header compression etc
Convergence support for 50 msec
Remote Provisioning -Auto/Zero touch
Clock distribution (Frequency, phase, time), Clock Recovery
Control plane and data plane security
Inter eNodeB X2 Traffic routing
Summary: any-to-any IP routing for unicast and multicast
59
* NGMN- Next Generation Mobile Network (Alliance of Mobile service Providers)
Mobile Backhaul Design Requirements
NGMNAlliance has released about 91 Requirements*
eNB –Multi-homing to MME/SGW (S1-Flex), RAN sharing
Max 16 S1 interfaces, 6 operators (S1-Flex)
Multicast Capability (eMBMS)
QoS -QCI to DSCP/CoSmapping, Shape, Rate limit
Bandwidth-LTE radio, other traffic (enterprise, WiFi)
BW optimization, header compression etc
Convergence support for 50 msec
Remote Provisioning -Auto/Zero touch
Clock distribution (Frequency, phase, time), Clock Recovery
Control plane and data plane security
Inter eNodeB X2 Traffic routing
Summary: any-to-any IP routing for unicast and multicast
© 2011 Cisco and/or its affiliates. All rights reserved.
60
Mobile Backhaul Bandwidth -Radio Behavior
Spectral
Efficiency
bps/Hz
Bandwidth, Hz
64QAM
16QAM
QPSK
cell
average
Busy Time
More averaging
UE1
UE2
UE3
: :
:
Many
UEs Quiet Time
More variation
UE1
64QAM
Cell average
UE1
bps/Hz
QPSK
Cell average
UE1
bps/Hz
Hz Hz
a) Many UEs / cell b) One UE with a good link c) One UE, weak link
BW is designed on per cell/sector, including each radio type
Busy time – averaged across all users
Quiet Time –one/two users (Utilize Peak bandwidth)
For multi-technology radio- sum of BW for each technology
Last mile bandwidth-Planned with Peak
Aggregation/Core –Planned with Meantime Average
Manage over subscription
60
Mobile Backhaul Bandwidth -Radio Behavior
Spectral
Efficiency
bps/Hz
Bandwidth, Hz
64QAM
16QAM
QPSK
cell
average
Busy Time
More averaging
UE1
UE2
UE3
: :
:
Many
UEs Quiet Time
More variation
UE1
64QAM
Cell average
UE1
bps/Hz
QPSK
Cell average
UE1
bps/Hz
Hz Hz
a) Many UEs / cell b) One UE with a good link c) One UE, weak link
BW is designed on per cell/sector, including each radio type
Busy time – averaged across all users
Quiet Time –one/two users (Utilize Peak bandwidth)
For multi-technology radio- sum of BW for each technology
Last mile bandwidth-Planned with Peak
Aggregation/Core –Planned with Meantime Average
Manage over subscription
© 2011 Cisco and/or its affiliates. All rights reserved.
61
Mobile Backhaul Bandwidth –Overheads
S1 User plane traffic
(for 3 cells)
+Control Plane
+X2 U and C-plane
+OA&M, Sync, etc
+Transport protocol overhead
+IPsecoverhead (optional)
Core network
RAN
123 4
X-2 user & control: ~ 3-5% (Applies only to Meantime Avg.)
OA&M, Sync: <1% covering S1-MME, OAM etc.
Transport GTP /Mobile IP Tunnel: ~10%
IPSec: Overhead of ~14%. Total of 1+2+3+4 ~25%
61
Mobile Backhaul Bandwidth –Overheads
S1 User plane traffic
(for 3 cells)
+Control Plane
+X2 U and C-plane
+OA&M, Sync, etc
+Transport protocol overhead
+IPsecoverhead (optional)
Core network
RAN
123 4
X-2 user & control: ~ 3-5% (Applies only to Meantime Avg.)
OA&M, Sync: <1% covering S1-MME, OAM etc.
Transport GTP /Mobile IP Tunnel: ~10%
IPSec: Overhead of ~14%. Total of 1+2+3+4 ~25%
© 2011 Cisco and/or its affiliates. All rights reserved.
62
Mobile Backhaul Bandwidth –Agg & Core
AGG AGG
ACC ACC
Star
Core/Super Backbone
CSN CSN
Agg Ring
COR COR
AGG AGG
AGG AGG
ACC ACC
CSN CSN
AGG AGG
AGG AGG
AGG AGG
ACC ACC
CSN
Agg RingAgg Ring
Access Ring Access Ring Access
Ring
Access
Aggregation
Cell Site
COR
COR
COR
Meantime
Average
Meantime
Average
Peak
Meantime Average from LTE
Factor other traffic
WiFi, Wireline, Apps,
ISP transit peering etc.
62
Mobile Backhaul Bandwidth –Agg & Core
AGG AGG
ACC ACC
Star
Core/Super Backbone
CSN CSN
Agg Ring
COR COR
AGG AGG
AGG AGG
ACC ACC
CSN CSN
AGG AGG
AGG AGG
AGG AGG
ACC ACC
CSN
Agg RingAgg Ring
Access Ring Access Ring Access
Ring
Access
Aggregation
Cell Site
COR
COR
COR
Meantime
Average
Meantime
Average
Peak
Meantime Average from LTE
Factor other traffic
WiFi, Wireline, Apps,
ISP transit peering etc.
© 2011 Cisco and/or its affiliates. All rights reserved.
63
Mean Peak overhead4% overhead10% overhead25%
(as load->
infinity)
(lowest
load)
busy time
mean peak
busy time
meanpeak
busy time
mean peak
busy time
mean peak
DL1: 2x2, 10 MHz, cat2 (50 Mbps)10.537.8 31.5 37.8 1.3 0 36.0 41.6 41.047.3
DL2: 2x2, 10 MHz, cat3 (100 Mbps)11.058.5 33.0 58.5 1.3 0 37.864.4 42.973.2
DL3: 2x2, 20 MHz, cat3 (100 Mbps)20.595.7 61.5 95.7 2.5 0 70.4105.3 80.0119.6
DL4: 2x2, 20 MHz, cat4 (150 Mbps)21.0117.7 63.0117.7 2.5 0 72.1129.5 81.9147.1
DL5: 4x2, 20 MHz, cat4 (150 Mbps)25.0123.1 75.0123.1 3.0 0 85.8135.4 97.5153.9
UL1: 1x2, 10 MHz, cat3 (50 Mbps) 8.020.8 24.0 20.8 1.0 0 27.522.8 31.226.0
UL2: 1x2, 20 MHz, cat3 (50 Mbps) 15.038.2 45.0 38.2 1.8 0 51.542.0 58.547.7
UL3: 1x2, 20 MHz, cat5 (75 Mbps) 16.047.8 48.0 47.8 1.9 0 54.952.5 62.459.7
UL4: 1x2, 20 MHz, cat3 (50
Mbps)*
14.046.9 42.0 46.9 1.7 0 48.051.6 54.658.6
UL5: 1x4, 20 MHz, cat3 (50 Mbps) 26.046.2 78.0 46.2 3.1 0 89.250.8 101.457.8
Scenario, from TUDR study
Tri-cell Tput
Total U-plane + Transport overhead
No IPsec IPsecX2 OverheadSingle CellSingle base station
All values in Mbps
Mobile Backhaul Bandwidth –Last Mile
Considerations
Use quiet time peak for each cell
Not all cells will peak at same time- Factor this for 3/6 sector eNB
Microwave –Number of hops, total bandwidth
Access ring will have dual homing to pre- agg
Total BW = DL + UL (20MHz, 2X2DL MIMO, 1X2UL MIMO) 105.3+42 ~ 145 Mbps
63
Mean Peak overhead4% overhead10% overhead25%
(as load->
infinity)
(lowest
load)
busy time
mean peak
busy time
meanpeak
busy time
mean peak
busy time
mean peak
DL1: 2x2, 10 MHz, cat2 (50 Mbps)10.537.8 31.5 37.8 1.3 0 36.0 41.6 41.047.3
DL2: 2x2, 10 MHz, cat3 (100 Mbps)11.058.5 33.0 58.5 1.3 0 37.864.4 42.973.2
DL3: 2x2, 20 MHz, cat3 (100 Mbps)20.595.7 61.5 95.7 2.5 0 70.4105.3 80.0119.6
DL4: 2x2, 20 MHz, cat4 (150 Mbps)21.0117.7 63.0117.7 2.5 0 72.1129.5 81.9147.1
DL5: 4x2, 20 MHz, cat4 (150 Mbps)25.0123.1 75.0123.1 3.0 0 85.8135.4 97.5153.9
UL1: 1x2, 10 MHz, cat3 (50 Mbps) 8.020.8 24.0 20.8 1.0 0 27.522.8 31.226.0
UL2: 1x2, 20 MHz, cat3 (50 Mbps) 15.038.2 45.0 38.2 1.8 0 51.542.0 58.547.7
UL3: 1x2, 20 MHz, cat5 (75 Mbps) 16.047.8 48.0 47.8 1.9 0 54.952.5 62.459.7
UL4: 1x2, 20 MHz, cat3 (50
Mbps)*
14.046.9 42.0 46.9 1.7 0 48.051.6 54.658.6
UL5: 1x4, 20 MHz, cat3 (50 Mbps) 26.046.2 78.0 46.2 3.1 0 89.250.8 101.457.8
Scenario, from TUDR study
Tri-cell Tput
Total U-plane + Transport overhead
No IPsec IPsecX2 OverheadSingle CellSingle base station
All values in Mbps
Mobile Backhaul Bandwidth –Last Mile
Considerations
Use quiet time peak for each cell
Not all cells will peak at same time- Factor this for 3/6 sector eNB
Microwave –Number of hops, total bandwidth
Access ring will have dual homing to pre- agg
Total BW = DL + UL (20MHz, 2X2DL MIMO, 1X2UL MIMO) 105.3+42 ~ 145 Mbps
© 2011 Cisco and/or its affiliates. All rights reserved.
64
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
012345678910
Gbps
Tricell eNodeBs
5: 4x2, 20 MHz, cat4 (150 Mbps)no IPsec
4: 2x2, 20 MHz, cat4 (150 Mbps)no IPsec
3: 2x2, 20 MHz, cat3 (100 Mbps)no IPsec
2: 2x2, 10 MHz, cat3 (100 Mbps)no IPsec
1: 2x2, 10 MHz, cat2 (50 Mbps)no IPsec
0.01
0.1
1
10
100
1000
1 10 100 1000 10000
Gbps
Tricell eNodeBs
single cell eNodeBs:
1 2 3 6 9 12 15 18 21 24 27 30
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
012345678910
Gbps
Tricell eNodeBs
5: 1x4, 20 MHz, cat3 (50 Mbps) no IPsec
4: 1x2, 20 MHz, cat3 (50 Mbps)*no IPsec
3: 1x2, 20 MHz, cat5 (75 Mbps) no IPsec
2: 1x2, 20 MHz, cat3 (50 Mbps) no IPsec
1: 1x2, 10 MHz, cat3 (50 Mbps) no IPsec
0.01
0.1
1
10
100
1000
1 10 100 1000 10000
Gbps
Tricell eNodeBs
single cell eNodeBs:
1 2 3 6 9 12 15 18 21 24 27 30
Mobile Backhaul Bandwidth –Agg & Core
Down link
Uplink
Total BW = DL + UL ; For 10,000 eNB (Tricell) = 700+500 = 1200 Gbps
Per eNB in Core ~ 1200/10,000 ~ 120 Mbps
64
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
012345678910
Gbps
Tricell eNodeBs
5: 4x2, 20 MHz, cat4 (150 Mbps)no IPsec
4: 2x2, 20 MHz, cat4 (150 Mbps)no IPsec
3: 2x2, 20 MHz, cat3 (100 Mbps)no IPsec
2: 2x2, 10 MHz, cat3 (100 Mbps)no IPsec
1: 2x2, 10 MHz, cat2 (50 Mbps)no IPsec
0.01
0.1
1
10
100
1000
1 10 100 1000 10000
Gbps
Tricell eNodeBs
single cell eNodeBs:
1 2 3 6 9 12 15 18 21 24 27 30
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
012345678910
Gbps
Tricell eNodeBs
5: 1x4, 20 MHz, cat3 (50 Mbps) no IPsec
4: 1x2, 20 MHz, cat3 (50 Mbps)*no IPsec
3: 1x2, 20 MHz, cat5 (75 Mbps) no IPsec
2: 1x2, 20 MHz, cat3 (50 Mbps) no IPsec
1: 1x2, 10 MHz, cat3 (50 Mbps) no IPsec
0.01
0.1
1
10
100
1000
1 10 100 1000 10000
Gbps
Tricell eNodeBs
single cell eNodeBs:
1 2 3 6 9 12 15 18 21 24 27 30
Mobile Backhaul Bandwidth –Agg & Core
Down link
Uplink
Total BW = DL + UL ; For 10,000 eNB (Tricell) = 700+500 = 1200 Gbps
Per eNB in Core ~ 1200/10,000 ~ 120 Mbps
© 2011 Cisco and/or its affiliates. All rights reserved.
65
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW/PGW, DNS, HSS, PCRF
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
65
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW/PGW, DNS, HSS, PCRF
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
© 2011 Cisco and/or its affiliates. All rights reserved.
66
LTE Network Security Threats
• Rogue eNB connecting to RIL MME.
• Resource Exhaustion on MME (too many
authentication requests from eNB)
• Mobile to Mobile Spewing Attacks
• DOS Attacks in downlink direction from Internet
• TCP based attacks from Internet (Syn, session hijack, resource exhaustion etc.)
• UDP Based attacks like Smurf attack.
• ICMP Attacks like ping of death. Fragmentation attacks.
• Layer 4 protocol anomalies attacks
• Malware/Spyware prevention
• Rogue MME connecting to HSS or PCRF
• HSS, PCRF protections against DOS/DDOS attacks
• Database (Sp) must be protected against protocol anomalies attacks
like SQL Slammer worm or resource consumption attacks.
• CDR protection against manipulation by both internal or external
attackers.
66
LTE Network Security Threats
• Rogue eNB connecting to RIL MME.
• Resource Exhaustion on MME (too many
authentication requests from eNB)
• Mobile to Mobile Spewing Attacks
• DOS Attacks in downlink direction from Internet
• TCP based attacks from Internet (Syn, session hijack, resource exhaustion etc.)
• UDP Based attacks like Smurf attack.
• ICMP Attacks like ping of death. Fragmentation attacks.
• Layer 4 protocol anomalies attacks
• Malware/Spyware prevention
• Rogue MME connecting to HSS or PCRF
• HSS, PCRF protections against DOS/DDOS attacks
• Database (Sp) must be protected against protocol anomalies attacks
like SQL Slammer worm or resource consumption attacks.
• CDR protection against manipulation by both internal or external
attackers.
© 2011 Cisco and/or its affiliates. All rights reserved.
67
Serving NodeAN
Home Node
Mobile Node
Provider AppsUser Apps
USIM
4
1
1
1
1
2
2
1
3
Transport
Application
Network
1
2
3
4
Network Access Securityin Radio Access
Network Domain Network security for signaling & user data
User Domain Security for mobile
Application DomainUser & Apps security
3GPP TS 33.401 Security Standards
67
Serving NodeAN
Home Node
Mobile Node
Provider AppsUser Apps
USIM
4
1
1
1
1
2
2
1
3
Transport
Application
Network
1
2
3
4
Network Access Securityin Radio Access
Network Domain Network security for signaling & user data
User Domain Security for mobile
Application DomainUser & Apps security
3GPP TS 33.401 Security Standards
© 2011 Cisco and/or its affiliates. All rights reserved.
68
SP Security Framework -COPM
Framework Recommendations
Identity LTE users (AAA and PCRF), Routing Authentication
Monitor PCEF/PCRF, IPS, Probes, Netflow , NBAR, Topology Map, DOS, DDOS
Correlate Security Operations Center(collect, correlatesecurity incidentsand alerts)
Harden ControlPlane Policing, VTTYlockdown, NTP, syslog, config mgmt
Isolate Contexts, Virtualization, Remote Triggered BlackHole
Enforce iACL, ACLs, Firewall,uRPF,QoS, Rate Limiting
68
SP Security Framework -COPM
Framework Recommendations
Identity LTE users (AAA and PCRF), Routing Authentication
Monitor PCEF/PCRF, IPS, Probes, Netflow , NBAR, Topology Map, DOS, DDOS
Correlate Security Operations Center(collect, correlatesecurity incidentsand alerts)
Harden ControlPlane Policing, VTTYlockdown, NTP, syslog, config mgmt
Isolate Contexts, Virtualization, Remote Triggered BlackHole
Enforce iACL, ACLs, Firewall,uRPF,QoS, Rate Limiting
© 2011 Cisco and/or its affiliates. All rights reserved.
69
Security for Roaming Traffic
IPSec tunnel between hDRA and vDRA to route control
traffic
User authentication traffic between vHSS and hHDSS
Policy traffic between hPCRF and vPCRF
GRX firewall to for user plane romaing traffic
For local breakout visited network provide internet security
UE UE
vPCRFhPCRF
PGW SGWeNB
MME
PGWSGW
MME
eNB
Home Network
Transit IP
Network(s)
Visited Network
Home routed (HR) traffic
Local breakout
(LBO)
GRX FW (User plane)
vHSShHSS
vDRAhDRA Control (IPSec)
69
Security for Roaming Traffic
IPSec tunnel between hDRA and vDRA to route control
traffic
User authentication traffic between vHSS and hHDSS
Policy traffic between hPCRF and vPCRF
GRX firewall to for user plane romaing traffic
For local breakout visited network provide internet security
UE UE
vPCRFhPCRF
PGW SGWeNB
MME
PGWSGW
MME
eNB
Home Network
Transit IP
Network(s)
Visited Network
Home routed (HR) traffic
Local breakout
(LBO)
GRX FW (User plane)
vHSShHSS
vDRAhDRA Control (IPSec)
© 2011 Cisco and/or its affiliates. All rights reserved.
70
Security for Backhaul
3GPP specifies IPSec for security Gateway for backhaul traffic
For RAN sharing Security gateway is must
IPSec will add overhead (~ 25%), Provision additional bandwidth
Many variations –S1-MME, S1-U, X-2, Management
X-2 is routed directly at
access ring.
Layer-3 at Cellsite Node
X-2 is routed through
shared RAN (Agg/Core)
using IPSec tunnel
70
Security for Backhaul
3GPP specifies IPSec for security Gateway for backhaul traffic
For RAN sharing Security gateway is must
IPSec will add overhead (~ 25%), Provision additional bandwidth
Many variations –S1-MME, S1-U, X-2, Management
X-2 is routed directly at
access ring.
Layer-3 at Cellsite Node
X-2 is routed through
shared RAN (Agg/Core)
using IPSec tunnel
© 2011 Cisco and/or its affiliates. All rights reserved.
71
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
71
Mobile Broadband Dynamics
Mobile Network Evolution
LTE Architecture Framework
LTE Design Strategies
Latency & Delay
IP Planning
MME, SGW, PGW, DNS
Transport Planning – Backhaul, MPLS Core
Security Framework
LTE Deployment Strategies
Summary, References
Agenda
© 2011 Cisco and/or its affiliates. All rights reserved.
72
LTE Deployment Strategies
Plan and Design [Getting ready]
IP Transformation- LTE readiness Assessment
Skillet –IPv6, LTE technology Trainings
Radio planning –site acquisition/readiness
Business Planning –services, subscribers
E2E LTE Design: Radio, Transport, Gateways, Datacenter, Apps
Test and Validation [Technology Validation]
E2E System integration and testing
System level IOT-All vendors, All related elements, All Apps
IRAT testing -2G/3G; Offload – WiFi, Femto
Device ecosystem testing, Apps testing
Roaming testing with other LTE networks
Field Trials, Friendly Users [Getting ready to Deploy]
E2E network validation with real users
KPI, Ops and troubleshooting tools,
NOC, OSS/BSS -Support structure
72
LTE Deployment Strategies
Plan and Design [Getting ready]
IP Transformation- LTE readiness Assessment
Skillet –IPv6, LTE technology Trainings
Radio planning –site acquisition/readiness
Business Planning –services, subscribers
E2E LTE Design: Radio, Transport, Gateways, Datacenter, Apps
Test and Validation [Technology Validation]
E2E System integration and testing
System level IOT-All vendors, All related elements, All Apps
IRAT testing -2G/3G; Offload – WiFi, Femto
Device ecosystem testing, Apps testing
Roaming testing with other LTE networks
Field Trials, Friendly Users [Getting ready to Deploy]
E2E network validation with real users
KPI, Ops and troubleshooting tools,
NOC, OSS/BSS -Support structure
© 2011 Cisco and/or its affiliates. All rights reserved.
73
LTE Deployment Strategies
Scaling in Deployment
Implementation Plans – Integration and Test automation
Scaling the architecture -Traffic Modeling, Virtualization
Tools development -Provisioning, Monitoring, IPv6
Knowledge Enhancement -Engineering and Ops
Operations and Optimize NOC-E2E IP infrastructure, centralized FCAPS
Centralize & automated IP Management
Security Operations (SOC)- consistent security implementation
Organization realignments – Engineering, Operations
Asset Lite, partner collaboration strategy
73
LTE Deployment Strategies
Scaling in Deployment
Implementation Plans – Integration and Test automation
Scaling the architecture -Traffic Modeling, Virtualization
Tools development -Provisioning, Monitoring, IPv6
Knowledge Enhancement -Engineering and Ops
Operations and Optimize NOC-E2E IP infrastructure, centralized FCAPS
Centralize & automated IP Management
Security Operations (SOC)- consistent security implementation
Organization realignments – Engineering, Operations
Asset Lite, partner collaboration strategy
© 2011 Cisco and/or its affiliates. All rights reserved.
74
Everything Put Together –How Does It Look?
74
Everything Put Together –How Does It Look?
© 2011 Cisco and/or its affiliates. All rights reserved.
75
2G, 3G, 4G Access
Vendor 1Vendor 1 Vendor 2 Vendor 3 Vendor 2 Vendor 3
Data
Center
IP Core
Packet
Core
Mobile
Backhaul
WiFi, Femto
Cisco EPC: Intelligent Performance
One Network, Any G, Any Screen
Comprehensive
Highly
Intelligent
Powerful
Performance
Flexible
Data Center
Switching
Policy
AAA
Billing
WAAS –Mobile
iControl Mobile Video
IP / MPLS / Core
2G, 3G, 4G, WiFi/FemtoGateway
Session Control (xCSCF, SIP)
IP RAN, Edge,
Aggregation
Nexus 5000
Nexus 7000
UCS
CRS
ASR 5000
ASR 9000
7600
ASR 903 ASR 901
ME 36/3800
75
2G, 3G, 4G Access
Vendor 1Vendor 1 Vendor 2 Vendor 3 Vendor 2 Vendor 3
Data
Center
IP Core
Packet
Core
Mobile
Backhaul
WiFi, Femto
Cisco EPC: Intelligent Performance
One Network, Any G, Any Screen
Comprehensive
Highly
Intelligent
Powerful
Performance
Flexible
Data Center
Switching
Policy
AAA
Billing
WAAS –Mobile
iControl Mobile Video
IP / MPLS / Core
2G, 3G, 4G, WiFi/FemtoGateway
Session Control (xCSCF, SIP)
IP RAN, Edge,
Aggregation
Nexus 5000
Nexus 7000
UCS
CRS
ASR 5000
ASR 9000
7600
ASR 903 ASR 901
ME 36/3800
© 2011 Cisco and/or its affiliates. All rights reserved.
76
Evolution of Cisco’s MITG Portfolio
Multimedia Services
Multimedia Services
S/I/P-CSCF
IP Telephony Features
Breakout Gateway
Access Border GW
WiFi
Fixed Mobile Core
Packet Data Interworking Function
Packet Data Gateway
Tunnel Termination Gateway
xDSL
Cable
FTTH
Femto
Femto Network Gateway
Home Node-B Gateway
Home eNode-B GW
Legacy Voice Convergence
Voice over LTE
Voice & Service Continuity
SMS Offload/IP-SMSC
MAP Femto Interworking Function
VoIP/WEB 2.0 Services
Multi-Media Telephony
Telephony Application Server
WEB 2.0/IMS 2.0
RCS
IP Services Gateway Policy & Charging Rules Function Online/Offline Charging Server
SGSN/GGSN/PCEF
MME/S-GW/P-GW
Mobile Packet Core
PDSN
Home Agent/EHA/PCEF
ASN Gateway
PCEF
Enhanced Charging
Content Filtering
Stateful Firewall
Network-based Traffic
Optimization
In-line Services
Application Detection
and Optimization
IMS Apps.
WEB
CDMA
UMTS
LTE
WiMAX
MSC
ASR 5000
76
Evolution of Cisco’s MITG Portfolio
Multimedia Services
Multimedia Services
S/I/P-CSCF
IP Telephony Features
Breakout Gateway
Access Border GW
WiFi
Fixed Mobile Core
Packet Data Interworking Function
Packet Data Gateway
Tunnel Termination Gateway
xDSL
Cable
FTTH
Femto
Femto Network Gateway
Home Node-B Gateway
Home eNode-B GW
Legacy Voice Convergence
Voice over LTE
Voice & Service Continuity
SMS Offload/IP-SMSC
MAP Femto Interworking Function
VoIP/WEB 2.0 Services
Multi-Media Telephony
Telephony Application Server
WEB 2.0/IMS 2.0
RCS
IP Services Gateway Policy & Charging Rules Function Online/Offline Charging Server
SGSN/GGSN/PCEF
MME/S-GW/P-GW
Mobile Packet Core
PDSN
Home Agent/EHA/PCEF
ASN Gateway
PCEF
Enhanced Charging
Content Filtering
Stateful Firewall
Network-based Traffic
Optimization
In-line Services
Application Detection
and Optimization
IMS Apps.
WEB
CDMA
UMTS
LTE
WiMAX
MSC
ASR 5000
© 2011 Cisco and/or its affiliates. All rights reserved.
77
Cisco MITG ASR 5000 Product Line
Software Decoupled from Hardware
Software functions work across multimedia core platforms
Platform decision based on performance not function
All multimedia core platforms support EPC, 3G, etc.
Next generation product line
GGSN
SGSN
MME
PGW
SGW
SCM
ASN GW
HA
PDSN
SeGW
In-Line
Services
Software
Functions
Hardware
Platforms
Performance & Scalability
ASR
5000
ASR 5000 Mobile Multimedia Platforms
HNB-GW
HeNB-GW
PCRF
77
Cisco MITG ASR 5000 Product Line
Software Decoupled from Hardware
Software functions work across multimedia core platforms
Platform decision based on performance not function
All multimedia core platforms support EPC, 3G, etc.
Next generation product line
GGSN
SGSN
MME
PGW
SGW
SCM
ASN GW
HA
PDSN
SeGW
In-Line
Services
Software
Functions
Hardware
Platforms
Performance & Scalability
ASR
5000
ASR 5000 Mobile Multimedia Platforms
HNB-GW
HeNB-GW
PCRF
© 2011 Cisco and/or its affiliates. All rights reserved.
78
1.NGMNhttp://www.ngmn.org(White paper on Gateways, backhaul, security)
2.4GAmericas http://www.4gamericas.org(Whitepapers)
3GPP Release 10 and beyond
IPv6 integration
GSN-UMTS migration to 4G
3.3GPP http://www.3gpp.org(Standards)
3GPP TR 34.401 General Packet Radio Service enhancements for (E-UTRAN) access
3GPP TR 36.913Requirement for E-UTRAand E-UTRAN
3GPP TR 35.913 Requirement for further enhancement of E-UTRA(LTE-Advanced)
3GPP TR23.975 IPv6 Migration Guidelines (R10)
4.ETSI Studies on latency requirements for M2M applications
http://docbox.etsi.org/Workshop/2010/201010_M2MWORKSHOP/
5.Global Certification Forum –Testing mobile devices
http://www.globalcertificationforum.org/WebSite/public/home_public.aspx
6.Ericsson white paper on Latency Improvements in LTE
http://www.ericsson.com/hr/about/events/archieve/2007/mipro_2007/mipro_1137.pdf
7.Techmahindrawhitepaper on Latency Analysis
http://www.techmahindra.com/Documents/WhitePaper/White_Paper_Latency_Analysis.pdf
References
78
1.NGMNhttp://www.ngmn.org(White paper on Gateways, backhaul, security)
2.4GAmericas http://www.4gamericas.org(Whitepapers)
3GPP Release 10 and beyond
IPv6 integration
GSN-UMTS migration to 4G
3.3GPP http://www.3gpp.org(Standards)
3GPP TR 34.401 General Packet Radio Service enhancements for (E-UTRAN) access
3GPP TR 36.913Requirement for E-UTRAand E-UTRAN
3GPP TR 35.913 Requirement for further enhancement of E-UTRA(LTE-Advanced)
3GPP TR23.975 IPv6 Migration Guidelines (R10)
4.ETSI Studies on latency requirements for M2M applications
http://docbox.etsi.org/Workshop/2010/201010_M2MWORKSHOP/
5.Global Certification Forum –Testing mobile devices
http://www.globalcertificationforum.org/WebSite/public/home_public.aspx
6.Ericsson white paper on Latency Improvements in LTE
http://www.ericsson.com/hr/about/events/archieve/2007/mipro_2007/mipro_1137.pdf
7.Techmahindrawhitepaper on Latency Analysis
http://www.techmahindra.com/Documents/WhitePaper/White_Paper_Latency_Analysis.pdf
References
© 2010 Cisco and/or its affiliates. All rights reserved.Cisco PublicBRKSPM-5288 79
Thank you.
Thank you.
Tags
Categories
DesignDownload
Download Slideshow Get the original presentation fileQuick Actions
Statistics
- Views 30
- Slides 79
- Age 597 days
Related Slideshows
1
MGV Residential Design projects for different clients, including a New Mexico Adobe project-1-.pdf
mannyvesa
41 views
16
EUNITED_Advocacy and Public Engagement through Visual Media
GeorgeDiamandis11
45 views
31
DESIGN THINKINGGG PPT 2 TOPIC IDEATION.pptx
HibaZaidi2
41 views
36
DESIGN THINKING CHAPTER 1 PPTT PPT 1.pptx
HibaZaidi2
48 views
112
Hinduism and Its History - PowerPoint Slides.pptx
ConorMcCormack10
42 views
20
Service Attributes of Manufactured Parts.pptx
MustafaEnesKrmac
39 views