Security Level:
www.huawei.com
Win from the Beginning -- Huawei EPC Evolution KEY Considerations HUAWEI TECHNOLOGIES CO., LTD.
Huawei Confidential
Opcos’ Steps of Convergent EPC Deployment 2010
2011
2012
2013
Telifonica- Germany T-Mobile- Germany Telenor-Sweden EE- UK Etsalat- UAE Mobily- Saudi Araba STC- Saudi Araba Zain- Kuwait M1- Singapore PCCW- Hongkong Phase 1: Partially Convergent EPC
Phase2: Fully convergent EPC
Among 102 Operators survey survey,, 84% will move to a convergent EPC core network. Convergent EPC Network SGSN/MME GERAN
experience : Less latency of GUL interworking • Better user experience:
• Higher network efficiency: efficiency : Reduce 20% inter-RAT signaling
UTRAN
LTE
(Source: HeavyReading 2012)
Benefits
• CAPEX saving: saving: 30% hardware hardware saved by resource sharing. GGSN/EPC-GW
• OPEX saving: saving: Simplicity of networking and O&M.
Key Considerations of EPC Convergence Evolution Proof • Optimized architecture for future network • Multiple access technology supported
Fast and Smoothly
EPC Concerns
• Faster deployment, shorter Go-to-Market • Reliability and less impact to live network
Cost-saving • Reuse existing equipment • GUL resource sharing
Better Experience • Less service interrupt and latency • Smooth GUL interworking and CS-like voice quality
OPCOs’ Key Concerns Evolution Proof • Optimized architecture for future network • Multiple access technology supported
Huawei’s Highlighted Solution Platform Continuity • Reuse the existing platform and in recent 10 years • Never switching platform frequently like others
Big Changes in EPC Era Different platform requirement of EPC & G/U
EPC architecture has big changes
Intelligence
UMTS NodeB
RNC
SGSN
GGSN
Sessions
5 4 3 2 1 0
Throughput
EPC
MME
LTE
G/U PS eNodeB
Source: HeavyReading Transactions
EPC-GW
1. Control plane and User plane’s separation 2. Flat architecture: MME connects with eNodeB directly 3. Always online 4. Higher throughput caused by LTE
1. 2. 3. 4.
MME does not need user plane resource MME needs to process more signaling EPC reserves more bearer context EPC needs more throughput
Huawei’s Position on Single Platform
• Share Control and User plane resource dynamically
• Future oriented high signaling capability and memory capacity
• Future oriented throughput
Blade Server Platform • Centralize deployment • For all control nodes not only PS/EPC • Clear future evolution to cloud com puting and SaaS
Service Router Platform • Local and distributed deployment for all access technologies
architecture
The strategy that ATCA for Signaling and PGP for forwarding plane is best Choice in LTE era
OPCOs’ Key Concerns Fast and Smoothly • Faster deployment, shorter Go-to-Market • Reliability and less impact to live network
Huawei’s Highlighted Solution Inherit 100% legacy features • Benefit from platform continuity, all the features don’t need to develop again in new platform
100% Service Continuity from Day One 100% Inherited of UGW9811
100% Inherited of USN9810
Decoupling HW & SW N S G S
E M M
d e s n e i b r u t m o a e C F
Enhanced Service Boards
Common hardware
Service Continuity
Decoupling HW & SW
Deployment Continuity E1/ATM/IP Interface Features Continuity 100% GU PS Feature Enhanced Continuity SGSN/MME combined Pool S4 SGSN & Gn/Gp SGSN Ultra-Flash CSFB
Same Service Experience
N S G G
W G P / S
d e s n e i b r u t m o a e C F
Enhanced Service Boards
Common hardware
Service Continuity SA Enhancement 1.3K Protocols ,enhanced TP Features Continuity IPSEC/ L2TP VPN Enhanced Continuity IPPM/IPSQM E2E Tracing PCC & Smartphone Visibility
Same Service Experience
OPCOs’ Key Concerns Cost-saving • Reuse existing equipment • GUL resource sharing
Huawei’s Highlighted Solution Deep Level Convergence • Single service board for everything. Control & user plane, G/U/L PDP resources, CPU, memory and Throughput
Deep Level Convergence User plane
Dedicated Board GPRS
for GPRS/UMTS/LTE
UMTS
Resources can not be shared between boards
LTE
GPRS
UMTS
Separated Board for user plane and signalling plane
Resources can not be shared between signalling boards plane
Inside Board G/U/L Unified Processor
Signaling Process
3
Packet Forwarding
Dynamic CPU Sharing Between signalling & User Plane
2
G/U/L Unified Memory PDP Context for G/U Bearer Context for LTE
Dedicated CPU/VCPU
CPU2
For PRS/UMTS/LTE or for user plane and signalling plane
GPRS
UMTS
CPU3 LTE
LTE
1
CPU1
Resources can not be shared between CPUs/VCPUs
Deep level Convergence Inside board, all resources are Board shared capacity 1. G/U/L Unified CPU 2. G/U/L Unified Memory 3. Dynamic CPU sharing between Idle capacity signalling & User Plane
LTE user increase↑ G/U user decrease↓
G/U used
Dynamic resource sharing reuses legacy hardware investment
LTE used
Huawei Advanced ATOM Level GUL Convergence One Board for G/U/L Access
One Board for CP+UP Plane
USN/UGW
G/U
USN/UGW
G/U
Control Plane Board
LTE
User Plane Board
Scenario 1
Scenario 2
Common Hardware
Common Hardware
Increasing # of LTE Users
LTE
CP
UP
CP
UP
Changing Traffic Conditions
Dynamic resource sharing in G/U/L access
CAPEX saved up to
Hardware
sharing in Control plane and User plane
30% by in-depth resource sharing solution
Reduce Inter-RAT Signaling, Improve User Experience Inter-RAT Signaling Saved 20% in Convergent Scenario
Scenario: Convergent EPC SGSN/MME
Intra-NE LTE
2G/3G
30 s e 20 g a s s e 10 M g n i l 0 a n g i S
18%
Scenario: Overlay EPC
SGSN
2G/3G
Inter-NE
25%
25% 15% 5% -5%
Cell-Reselection Overlay EPC
G/U/L Interworking changed to Intra-NE process
18%
Attach
Handover
Convergent EPC
Saved Msgs
Enhanced User Experience during Inter-RAT Handover
8%
36%
46%
MME
LTE
Separate SGSN & MME
Convergent SGSN & MME
Inter-RAT handover success rate
G/U to LTE
LTE to G/U
Inter-RAT handover latency
Share the System Resource, Optimized TCO System Configuration Comparison
Common hardware for GUL access
18.2% GPRS
UMTS
23.5%
32.2%
One Board for GPRS, UMTS, LTE Access One Board for User-plane and control-plane handling
ESU
LTE
Dynamic Resource Sharing Idle capacity G/U used Board capacity
LTE user increase↑
LTE used
G/U user decrease↓
All hardware resources are shared in board
Based Huawei traffic model
Hardware Configuration:
SAU in Phase 1: G/U 1.6M + EPC 0.4M VS. Convergence 2M
SAU in Phase 2: G/U 1M
SAU in Phase 3: G/U 0.4M + EPC 1.6M VS. Convergence 2M
+ EPC 1M
VS. Convergence 2M
Hardware saved up to 30% by common board
Only license activated for LTE user increase
OPEX saved up to 30% by common O&M
OPCOs’ Key Concerns Better Experience • Less service interrupt and latency • Smooth GUL interworking and CS-like voice quality
Huawei’s Highlighted Solution Leading Commercial Experience • No.1 in GU and EPC commercial deployment • Abundant E2E product line and IOT experience
70+ Launched &110+ Contracts of EPC Commercial Networks Europe
CIS Americas
APAC MEA
1st convergent SGSN/MME Pool
1st commercial
1st commercial GUL
VoLTE network
convergent network
1st commercial LTE MOCN By the end of May, 2013
DT: WORLD’S 1ST G/U/L CONVERGENT NETWORK ORIGIN
• Leading operator in Germany, 35M
SOLUTION
users, operating GSM, UMTS & LTE networks
• Telekom selected Huawei as the sole
Max: 152Mbps
vendor for entire G/U PS networks
Ave: 131Mbps
• LTE is planned to deploy across
RESULT
Germany, providing higher bandwidth & improving radio coverage
DD800
• Huawei wins LTE/EPC contract in
End-to-end
2010Q1, and wins GSM modernization contract in 2010Q4
• Anchor G/U/L traffic on convergent gateway, UGW9811, in May 2011
• “I have to say, today I am a really happy customer because you surprised me and our people that you can do what we S o l e G U L P S V e n d o r wanted so fast and with such good quality.” -- Dr. Solvie, PS Director of Deutsc h Telekom
CPE
USN SingleRAN: GSM900 + GL1800 + LTE2.6G
UGW
SingleEPC
LTE DL Throughput
delivery including: terminal, radio part & PS core G/U/L convergent solution serving new LTE users & existing G/U users Ranks No.1 in the LTE live test, reaching 152Mbps Inheritable Features • Experience the
• Future-proof platform
• SingleEPC &
same features
to protect investment
SingleRAN serving
among G/U/L to
• Advanced technology
G/U/L within one site
guarantee the
for high throughput
to make O&M simple
service integrity
Unified Platform
Single Network
Huawei successfully builds the world’s 1st convergent PS serving G/U/L users
Other KEY Concerns
Centralize or De-Centralize of EPC-GW ? Distributed EPC-GW
Centralized EPC-GW
EPC-GW
SGSN/MME
POP
Backhaul-1
Backhaul-1
POP
Backbone
Backbone IDC/ Cache
Backhaul-2
SGSN/MME
EPC-GW
IDC/ Cache
Backhaul-2 EPC-GW
Factor
Centralized EPC-GW
Distributed EPC-GW
• More delay of local service (e.g. VoLTE) • Reduce delay about 4ms per 500Km transmission, for VoLTE and local Internet access • Unified management for VPN service • More transmission for LTE and 3GDT • Reduce 2Gbps per 1 million VoLTE user. Cost of user • Reduce transmission for Internet service, is dependent on Transmission • Hierarchical layer architecture for 2G
User experience
deployment of IDC/cache
users O&M
Proposal
• Less sites and simple O&M, reduce OPEX
• • •
• More sites and complex O&M *Note: Centralized SGSN-MME is assumed
Centralized GGSN/EPC-GW or same site with legacy GGSN is recomm ended in beginning phase EPC-GW is distributed with position of IDC/Cache and growth of VoLTE user. Keep some centralized EPC-GW for VPN service, 2G and roaming-out user.
Separated S-GW and P-GW or Integrated One ? Integrated S/P-GW
Separated S-GW and P-GW Roaming traffic
Roaming traffic backbone
P-GW
backbon e
Internet
S8
P-GW
Internet
S8 Local traffic
S-GW
S5
P-GW
Local traffic
S-GW
Internet
Save 35% hardware, lower CAPEX Share common S/PGW context and CPU process Intra S5 interface, reduce the inter-signaling process Core network backbone savings Fewer physical nodes, lower OPEX Simple networking, better QoE Reduce the delay between S-GW and P-GW
Proposal
•
S5
backbon e
P-GW
Internet
Flexible Deployment, separated expansion plan Add/upgrade S-GW for LTE access Add/upgrade P-GW for WiFi or PCC expansion Independently optimized for different functions S-GW focus on 3GPP access and mobility management P-GW focus multi-access and service management (DPI, PCC).
Integrated S/P-GW is recommended, while it can be separated logically in functions for roaming and special service (dedicated P-GW), etc.
How can legacy SGSN find Convergent GW? •
SGSN should select GGSN/EPC-GW, which acts as anchor point for service continuity, for G/U/L interworking scenario.
Available Solution
Cons.
Separate APN for GU and LTE
Configure new APN for LTE subscribers
Dedicated IMSI Segment for LTE Same APN and IMSI Segment for GU and LTE ARD (Access Restriction Data)
√
1. LTE user have separate IMSI segments 2. Not applicable for roam in users Upgrade legacy SGSN supporting GW selection by ARD and/or MS Network Capability MS Network Capability
GW selection
LTE Not Allowed
LTE supported
Legacy GGSN
LTE Not Allowed
LTE Not supported
Legacy GGSN
LTE Allowed
LTE supported
GGSN/EPC-GW
LTE Allowed
LTE Not supported
Legacy GGSN
Pros. No requirement on legacy SGSN No requirement on legacy SGSN Better user experience and simple provisioning HLR
GGSN/ EPC-GW
GGSN
ARD
SGSN
SGSN/ MME Network capability
GU user
GUL user
Should I Deploy Combined SGSN/MME Pool ? Advantage of Combined Pool
Combined SGSN/MME Pool SGSN /MME
SGSN /MME
SGSN /MME
1
SGSN/MME during G/U/L handover
3
2
Same serving anchor point in the
IP Transmission
Reduce signaling and latency during G/U/L handover, improve user experience
Load sharing in pool area, improve the system resource utilization
GSM
1
Proposal
LTE
UMTS
2
• •
3
Higher reliability in pool, no impact to single node failure
3
Combined SGSN/MME pool is recommended regardless of centralized or distributed SGSN/MME deployment Joint planning of NRI and MMEC from day one
When is The Best Time of S4 SGSN Deployment ?
Only S4 SGSN is supported in 3GPP Only S4 SGSN is supported in 3GPP
Needs S-GW anchor traffic
Needs S-GW anchor traffic
Benefit:
Benefit:
Benefit:
Benefit:
Simplified QoS model • QCI • GBR • AMBR
Handover between WiFi and G/U for service continuity
Totally separated between control plane and data plane
Reduce the signaling
Challenge:
Prerequisites:
Puzzle: • All NEs need upgrade • No much effect when
Proposal :
UE is not mature
Need convergent GW
there are few G/U/L UEs
Benefit is not important because RNC/BSC still use Pre-R8 QoS, but not E2E R8 QoS
Proposal:
Proposal:
Proposal:
Deploy in Phase3
Deploy in Phase3
Optional in Phase3
Proposal
1. Keep Gn/Gp SGSN before all above are ready 2. Upgrade to S4 SGSN together with the upgrade to combined SGSN/MME
Huawei Flexible S4 Interface Selection Solution PLMN
GUL user selected S4, others selected Gn interface
UE capability
GU Terminal s
USN
Gn GSM/U MTS
SGSN
GGSN S4
Gn/Gp Configurable Gn/S4 Select Policy LTE
S3/S4
MME
S-GW
GGSN /P-GW
GUL Terminal s
Local user selected S4, roaming-in user selected Gn PLMN/IMSI series
UE capability
Selected interface
123XXXXX
EPC
S4
123XXXXX
Non -EPC
Gn/Gp
345XXXXX
Any
Gn/Gp
Configurable policy for Gn/S4 interface selection
Flexible scenarios support for GUL interworking
Roaming user
HPLMN GSM/U MTS
Gn SGSN
GGSN
S4
LTE Local user
MME
S-GW
GGSN /P-GW
How to Deploy International Roaming ? GRX/IPX
MME
DNS
Router BG
eNodeB
DNS
•
Option1: Dedication GGSN&P-GW for international roaming traffic
•
Option2: GW proxy redirect UE to home GGSN&P-GW
DRA
DNS
BG PGW GGSN
S/PGW
Service Platform
Service Platform Visiting Network
Home Network
GRX/IPX
MME BG eNodeB
Router DRA DNS
DNS BG
S/PGW Service Platform
Visiting Network
Proposal
GW Proxy
Home Network
1. 2.
PGW GGSN
PGW GGSN
Home routing mode is recommended for first phase, local breakout is not mature for billing/settlement. Inherit G/U existing mode, upgrade/switch existing GGSN or GGSN proxy to GGSN&P-GW or GW proxy.
Summary of Huawei’s EPC Convergence Solution OPCOs’ Key Concerns Evolution Proof • Optimized architecture for future network • Multiple access technology supported
EPC Concerns
Fast and Smoothly • Faster deployment, shorter Go-to-Market • Reliability and less impact to live network
Cost-saving • Reuse existing equipment • GUL resource sharing
Better Experience • Less service interrupt and latency • Smooth GUL interworking and CS-like voice quality
Huawei’s Highlighted Solution Platform Continuity • Reuse the existing platform and in recent 10 years • Never switching platform frequently like others
Inherit 100% legacy features • Benefit from platform continuity, all the features don’t need to develop again in new platform
Deep Level Convergence • Single service board for everything. Control & user plane, G/U/L PDP resources, CPU, memory and Throughput
Leading Commercial Experience • No.1 in GU and EPC commercial deployment • Abundant E2E product line and IOT experience
Other Key Concerns Centralize or De-Centralize of EPC-GW ?
• •
Centralized GGSN/EPC-GW or same site with legacy GGSN is recommended in beginning phase EPC-GW is distributed with position of IDC/Cache and growth of VoLTE user.
Separated S-GW and P-GW or Integrated One ?
•
Integrated S/P-GW is recommended, while P-GW can be separated logically for roaming and special service
How can legacy SGSN find Convergent GW? • Huawei’s GW selection via ARD & MS Capacity is the best way to fulfill requirement in EPC’s Overlay scenario Should I Deploy Combined SGSN/MME Pool ?
•
Combined SGSN/MME pool is recommended regardless of centralized or distributed SGSN/MME deployment
When is The Best Time of S4 SGSN Deployment ? • Remain Gn/Gp SGSN before R8 QoS / WiFi HO / R8 DT / ISR are ready How to Deploy International Roaming ? • Inherit G/U existing mode, upgrade/switch existing GGSN or GGSN proxy to GGSN&P-GW or GW proxy.
Thank you www.huawei.com
Contact Me:
Mia Tang (Vietnam Huawei Wireless MKT)
[email protected] +84 0927421111
